4 ms·

"get a timestamp error if one node attempts to read data that was written by another node in the future (due to data moving across datelines)" Honest question:

by aidos 14y ago

"get a timestamp error if one node attempts to read data that was written by another node in the future (due to data moving across datelines)" Honest question: Which part of a replication/db system would be using time stamps that weren't universal?

donavanm 14y ago
Just the concept of using time for the logical clock is sketchy. It's not monotonically increasing, it drifts, it can go decrease, etc... Curious what their cross host/region ordering and consistency looks like.
- sanxiyn 14y ago
  "An atomic clock is not that expensive." -- http://research.google.com/archive/spanner.html http://research.google.com/archive/spanner.html
  - mikecb 14y ago
    Especially since there are 24 circling the earth that send out time continuously.
  - jrockway 14y ago
    Indeed. A GPS clock accurate to 50ns is around $25 on eBay.
- deleted 14y ago
  [deleted]
blrgeek 14y ago
And that's the part that Google Spanner gets around with Atomic clocks and GPS clocks.