Have a look in org.apache.cassandra.net:type=FailureDetector
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclustr.com
<https://support.instaclustr.com/hc/en-us>
This email has been sent on behalf of Instaclustr Limited (Australia) and
I
e the nodes showing any other signs of stress? CPU, GC, etc? Is there
anything pending in nodetool tpstats?
Regarding the read repairs, have you tested writing at a higher consistency
to see if that changes the number of RR occurring?
*Brooke Jensen*
VP Technical Operations & Customer
Like I said,
test in a lower environment first with your data model to be sure.
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclustr.com
<https://support.instaclustr.com/hc/en-us>
This email has been sent on behalf of Instaclus
3.7
<https://www.instaclustr.com/blog/2016/10/19/patched-cassandra-3-7/> which
backports some key patches from 3.9.
https://github.com/instaclustr/cassandra
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclustr.com
<https://support.instaclustr.com/hc/en-u
downtime.
Regards,
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclustr.com
<https://support.instaclustr.com/hc/en-us>
This email has been sent on behalf of Instaclustr Limited (Australia) and
Instaclustr Inc (USA). This email and any attac
ongoing
management of the cluster a lot easier.
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclustr.com
<https://support.instaclustr.com/hc/en-us>
This email has been sent on behalf of Instaclustr Limited (Australia) and
Instaclustr Inc (
Hi.
Can you please show me the specific error message you are receiving, as
well as the schema for this table (you can use the cql command "describe
table").
*Brooke Jensen*
VP Technical Operations & Customer Services
www.instaclustr.com | support.instaclu
