Hi, I've got the same problem
Upgraded from 2.2.11 to 3.11.3 and since then the DEBUG logs shows this
messages.
Seems to me that after the repair the messages were reduced a little, but
it's still happening.
In my case is a 3-node cluster, RF3, reads and writes with LOCAL_QUORUM
Felipe Esteves
Hi,
I have tested Cassandra 3.0.10 and 3.0.17 and I have found three potential bugs
there.
The test steps with CCM are as follows:
1) Start 3 node cluster
2) Create enough data with cassandra-stress
3) Kill node3
4) Create + Start node4 with replace_address=node3
5) Wait for streaming to start
Hi,
I have a question regarding token distribution with vnodes and
Murmur3Partitioner.
According to the documentation, the Murmur3Partitioner generates tokens
in the range from -9223372036854775808 to 9223372036854775807.
I have the following environment, _simplified_ for demo purposes:
-
