Dataloss at GitLab | PostgreSQL Blog | 2ndQuadrant
> pg_basebackup first issues a checkpoint to ensure it gets the latest data for the backup, which by default is a paced checkpoint to avoid hitting the disks too hard. As a result it can take a few minutes, typically about 4 minutes with default settings to start up. During that time the pg_basebackup process is quiet while it waits for the checkpoint on the master to complete. Seems like this cou
GitLab Live Stream
Working on restoring GitLab.com. FAQ below. * Blog post https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/ * Who did it, will they be fired? Someone made a mistake, they won't be fired. * The audio is too low, can you fix it? No, we're sorry. * Why is the restore so slow? We're limited by the disk speed of a non-production machine. * Size of the DB? 310GB * How long will t
GitLab.com database incident
GitLab.com database incident Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippets, etc.) for GitLab.com. Update: please see our postmortem for this incident Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippet
GitLab.com Database Incident - 2017/01/31
This incident affected the database (including issues and merge requests) but not the git repo's (repositories and wikis). Timeline (all times UTC): 2017/01/31 16:00/17:00 - 21:00 YP is working on setting up pgpool and replication in staging, creates an LVM snapshot to get up to date production data to staging, hoping he can re-use this for bootstrapping other replicas. This was done roughly 6 hou
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
