Re:NewSQL databases fail to guarantee consistency and I blam...
by jgalentine007 on Friday September 21, 2018 @10:59AM
(#18040167)
Thanks for pointing that out - I have yet to rtfm and dive deep. I wonder how frequently time sync problems occur in virtual environments after ntp syncing - I've seen pretty erratic behavior on virtual active directory domain controllers even after syncing with hyper-v and vmware.
[ Parent
| on HN ]
Re:NewSQL databases fail to guarantee consistency and I blam...
by brazzledazzle on Friday September 21, 2018 @04:14PM
(#18042346)
It’s been a long time since I messed with domain controllers but I believe Microsoft used to have explicit guides for handling time on virtual DCs. At that time we kept around a a couple hardware DCs to be safe but I do remember having the VMware agent correct the time could result in some bad results. I think it was because it immediately fixed the time and didn’t slowly correct the drift but it’s been a long time so my memory could be off.
Re:NewSQL databases fail to guarantee consistency and I blam...
by gurjeet on Friday September 21, 2018 @09:07PM
(#18043893)
Here’s their blog post on how they manage to live without atomic clocks. I’ve found at least one assumption of thiers that i don’t agree with, but notwithstanding that, it’s a good read.
https://www.cockroachlabs.com/blog/living-without-atomic-clo...
Re:NewSQL databases fail to guarantee consistency and I blam...
by amaccuish on Friday September 21, 2018 @07:11PM
(#18043364)
Time shouldn't be a massive issue for AD no? It's a vector clock, not a UTC clock. The UTC clock is only used to solve conflicts no?
Re:NewSQL databases fail to guarantee consistency and I blam...
by e12e on Saturday September 22, 2018 @08:17AM
(#18045703)
Why do you say that? I thought kerberos depended on timestamps +/- drift?
https://tools.ietf.org/html/rfc4120#section-5.2.3
Or do you mean some other part of AD?