3 ms·
Excellent postmortem. They blame their code and Golang, but another problem is that their kernel ran time backwards to implement the leap second. That's really
by NelsonMinar 10y ago
Excellent postmortem. They blame their code and Golang, but another problem is that their kernel ran time backwards to implement the leap second. That's really not the right way to do leap seconds, but is a common kludge because POSIX defines days as always having exactly 86,400 seconds. Details on that: https://en.wikipedia.org/wiki/Unix_time#Encoding_time_as_a_number https://en.wikipedia.org/wiki/Unix_time#Encoding_time_as_a_n...
- zigzigzag 10y agoIt's not the kernel's fault. The kernel provides several clocks, one of which is defined to be monotonic. However Go does not expose that clock.