So the coordinators could be made to hang around, replying on quorum and other
events, then dispatching an event when everything's been updated? I assume the
interested code would register an event hook on the bucket properties like a
commit hook?
jb
On Feb 28, 2011, at 5:10 PM, Sean Cribbs w
Ah, I misunderstood you. This would be an interesting addition to Riak, but is
not in the current roadmap. The request coordinators currently reply and exit
as soon as quorum is met, even if that's 0, so the replies from the vnodes
never get delivered if the coordinator is gone.
Sean Cribbs
De
Correct me if I'm wrong but you write a high-performance app by specifying
dw=all on every write. I'm thinking something along the lines of "take your
time inserting the data, just let me know when you're finished". That's
drastically different from "don't return from this call until you've writ
This is handled in Dynamo-style architectures like Riak with quorums. In
Riak's case, you rely on the "W" and "DW" quorum values to determine what is an
acceptable threshold for considering a write to be a success. By default, W
and DW are set to "quorum", which means N/2+1 (for N=3, this is 2
In the midst of a discussion about messaging and eventual consistency and I'm
wondering if there's a reasonable answer to the question:
Is eventual consistency in a system that needs to know when it can start
querying the system for the just-inserted data not a problem if there is an
event trig
