4 ms·
Talking with ops folks at work, they have seen system clocks in our fleet (which run ntpd) suddenly report times off by _years_ and then go back to "accurate."
by sethammons 7y ago
Talking with ops folks at work, they have seen system clocks in our fleet (which run ntpd) suddenly report times off by _years_ and then go back to "accurate." We have thousands of nodes for the software I work on. We sometimes get negative times when comparing events, if only by a few seconds. You can't fully trust time in a distributed system.
- aidenn0 7y agoSure, but it's also possible to write a word out to memory and then read something different back. There are probably many DBs that fail to meet their requirements when that happens. My sense is that time errors are much more common, but I'm interested in actual data surrounding that.