HI Bo;
you raised 2 questions:
20% system utilization
Hints
20% system utilization: For a node or a cluster to have 20% utilization is
Normal during peak write operation.
Hints: hints are written when a node is unreachable;C* 3.0 has a
complete over haul in the way hints have
thing in the documentation, but I
> cannot see any description of when hints are written other than when a node
> is marked as being down. And since none of our nodes have been marked as
> being down (at least according to the logs), I suspect that there is some
> timeout that governs
Hi Jens,
Thank you for the tip!
ALL would definitely cure our hints issue, but as you note, it is not
optimal as we are unable to take down nodes without clients failing.
I am most probably overlooking something in the documentation, but I cannot
see any description of when hints are written
how do you unsubscribe
From: Bo Finnerup Madsen <bo.gunder...@gmail.com>
Sent: Wednesday, April 20, 2016 9:38 AM
To: user@cassandra.apache.org
Subject: When are hints written?
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives write
Hi Bo,
> In our case, I would like for the cluster to wait for the write to be
persisted on the relevant nodes before returning an ok to the client. But I
don't know which knobs to turn to accomplish this? or if it is even
possible :)
This is what write consistency option is for. Have a look at
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives writes
from ~20 clients. The clients will write as fast as they can, and the whole
process is limited by the write performance of the cassandra cluster.
After we have tweaked our schema to avoid large partitions, the load is
