Re:NewSQL databases fail to guarantee consistency and I blam...
by jgalentine007 on Friday September 21, 2018 @10:10AM
(#18039796)
I recently came across CockroachDB and thought it's capabilities interesting, almost too good to be true. I also have been looking at Citus Data which shards and distributes transactions, are you aware of any consistency shortcomings with it?
[ Parent
| on HN ]
Re:NewSQL databases fail to guarantee consistency and I blam...
by cube2222 on Friday September 21, 2018 @10:35AM
(#18039961)
CockroachDB's performance is dependent on time synchronization. If a node detects it's too far behind, it will commit suicide.
However, before it detects it, there is a possibility of stale reads.
https://www.cockroachlabs.com/docs/stable/recommended-produc...
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.
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?
Re:NewSQL databases fail to guarantee consistency and I blam...
by amaccuish on Monday September 24, 2018 @06:35AM
(#18056500)
It defaults to 5 minutes. I perhaps wrongly assumed the issue was within 5 minutes.
Re:NewSQL databases fail to guarantee consistency and I blam...
by atombender on Friday September 21, 2018 @05:00PM
(#18042620)
My experience from test workloads on Cockroach is that single transaction performance is very bad compared to something like Postgres -- with 2.0 I was seeing easily 10x worse performance than Postgres with a three-node test cluster on Google Cloud. My impression is that it's worse for apps that have lots of small CRUD transactions on low numbers of rows, as is typical with web/mobile UIs.
Aggregate cluster performance seemed very good, though; i.e., adding a bunch more concurrent transactions did not slow down the other transactions noticeably.