Re:GitLab Database Incident – Live Report
by craigkerstiens on Tuesday January 31, 2017 @10:42PM
(#13538034)
I'm not sure there is a "late" at night or tired in the incident report. All times are UTC and it's unclear where all the team is located but if in SF then this is at 4pm which is when the incident just occurred. It doesn't necessarily change that you shouldn't be firefighting for extremely long cycles in hero-mode for that long, but not exactly the same as exhausted and powering away for hours.
[ Parent
| on HN ]
Re:GitLab Database Incident – Live Report
by Scriptor on Tuesday January 31, 2017 @11:30PM
(#13538250)
Gitlab's team is worldwide. YP seems to be someone in EU time, which right now is UTC+1.
That would mean that the incident happened around 11pm or midnight in YP's local time.
Re:GitLab Database Incident – Live Report
by YorickPeterse on Wednesday February 01, 2017 @05:01AM
(#13539578)
Correct, I'm based in Europe/Amsterdam so this happened mostly during the evening.
Re:GitLab Database Incident – Live Report
by sbuttgereit on Tuesday January 31, 2017 @11:29PM
(#13538247)
Actually, there is a brief comment:
"At this point frustration begins to kick in. Earlier this night YP explicitly mentioned he was going to sign off as it was getting late (23:00 or so local time), but didn’t due to the replication problems popping up all of a sudden."