The hsha (half-synchronous, half-asynchronous) Thrift server was
rewritten on top of Disruptor for Cassandra 2.0 [1] to unlock
substantial performance benefits over the old hsha. Unfortunately,
the rewrite introduced a bug that can cause incorrect data to be sent
from the coordinator to replicas.
Hi,
I have 7 nodes in cluster version 2.1.11 replication 3, 4 with this problem
above, and 3 is ok.
Anyone know what the hell is happening with these 4 nodes
[default@prod] list counterCF ;
Using default limit of 100
Using default cell limit of 100
null
TimedOutException()
at
Note that article pretty much covers it all; the nice thing about rapid-read
protection is that the dynamic snitch works on a per node statistics level to
pick which node(s) (in this case one), so a single poorly performing table
(perhaps corrupted SSTables on that node causing no responses and
