Data Loss at GitLab

I don't get to work on databases this size and today has been an incredible lesson and a journey. I've been reading all the comments and blogs, watching the stream and Googling what I didn't know or understand.

I feel like the next step for me is scaling my business so that we have an actual usage for my newly found interests :)

Re: Data Loss at GitLab

#7

Post by cornedor » Wed, Feb 01, 2017, 7:40 PM UTC

wheelerwj wrote: post #2

i wish everything was discussed/handled as publicly and transparently as this whole scenario. i really hope this becomes a thing.

I totally agree, the live stream [1] is amazing, discussing steps in the open like that and if there is some time left answer questions from the YouTube chat.

[1] https://www.youtube.com/c/Gitlab/live

Re: Data Loss at GitLab

#8

Post by hyperpape » Wed, Feb 01, 2017, 7:45 PM UTC

I'm surprised by the statement that 4 gigs of replication lag is normal. However, I don't manage backups for anything larger than personal pet projects, so I don't have a sense of scale.

Re: Data Loss at GitLab

#9

Post by willemmali » Wed, Feb 01, 2017, 8:02 PM UTC

jwilk wrote: post #4

https://news.ycombinator.com/item?id=13537052

^ Related HN discussion on the live report @ Google Docs

Re: Data Loss at GitLab

#10

Post by sulam » Wed, Feb 01, 2017, 8:11 PM UTC

neals wrote: post #6

I don't get to work on databases this size and today has been an incredible lesson and a journey. I've been reading all the comments and blogs, watching the stream and Googling what I didn't know or understand. I feel like the next step for me is scaling my business so that we have an actual usage for my newly found interests :)

Then you end up having deep expertise in a topic that's only important for larger companies. Sometimes this works out well, sometimes it leaves you a little stuck. :)