Hello,
Kindly post below details
1. Nodetool cfstats for both the tables.
2. Nodetool cfhistograms for both the tables.
3. Replication factor of the tables.
4. Consistency with which write requests are sent
5. Also the type of write queries for the table if handy would also help
(Light weight t
Hello Bobbie,
Do revert with below details:
1. Replication factor of the keyspace.
2. Consistency level used for read requests
3. Nodetool netstats output
4. grep “DigestMismatch” /log/directory/path/debug.log
Thanks
On 2019/07/18 17:19:10, Bobbie Haynes wrote:
> I have updated all the nodes
I have updated all the nodes in the cluster dcread_repair_chance to 0.0
stilll i see lot of messages.
On Thu, Jul 18, 2019 at 10:13 AM Bobbie Haynes
wrote:
> Hi,
> We are using Apache Cassandra 3.11.4 .Recently we are seeing
> overloaded readrepair ERROR messages in the entire cluster becau
Hi,
We are using Apache Cassandra 3.11.4 .Recently we are seeing
overloaded readrepair ERROR messages in the entire cluster because that we
are getting timeouts ..I'm not able to find the root cause for this .
Appreciate any inputs on this issue ..
ERROR [ReadRepairStage:2537] 2019-07-18 1
Hi all,
Our cassandra cluster consist of two dc and every dc we have 10 nodes. We
are using DSE 5.1.12 (cassandra 3.11).We have a high local write latency on
a single table. All other tables in our keyspace have normal latencies
like 0.02 msec,even tables that have more write tps and more data. B
