Hi,
1) and 2) I understand it the same way you do :-).
> 3) Node is up and receives the write but is too overloaded to handle it
> and drops the mutation. This should be visible in tpstats as dropped
> mutation. Does the write still stay in the hinted handoff table of the
> coordinator and if so
Hi,
I'm trying to reason the possible scenarios when a node of a C* cluster is
not getting the writes and the data needs some sort of anti-entropy
(repair, read-repair, etc.). In what cases does the coordinator not realize
that a write failed and doesn't replay the write from hinted handoff table?