Cassandra is last writer wins... according to the client timestamp? What the fucking fuck? (via @fowlduck)
-
-
Replying to @therealadam
@therealadam orly! eeeenteresting. I'm still confused why they don't use a server timestamp instead of a client one3 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@therealadam so the timestamp doesn’t have to be the current time only, it could be in reference to when an event occurred3 replies 0 retweets 0 likes -
Replying to @fowlduck
@fowlduck@therealadam the obvious disadvantage is that any clock skew on the client propagates throughout the system1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@therealadam that, or the wrong write wins. data loss ftw1 reply 0 retweets 0 likes -
Replying to @fowlduck
@fowlduck@therealadam yeah, that's what I'm referring to. Clock skew can mess up the causal ordering. Seems bad.1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@therealadam I’m pretty sure you can (and ppl do) retrieve those timestamps as well, so it can do more than just mess up causality1 reply 0 retweets 0 likes
@fowlduck @therealadam I'm trying to design a system that uses client-side timestamps, but it's a P2P system so I have an excuse ;)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.