cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Chandler <>
Subject Re: All time blocked in nodetool tpstats
Date Wed, 10 Apr 2019 11:55:21 GMT
Hi Abdul,

When I have seen dropped messages, I normally double check to ensure the node not CPU bound.

If you have a high CPU idle value, then it is likely that tuning the thread counts will help.

I normally start with concurrent_reads and concurrent_writes, so in your case as reads are
being dropped then increase concurrent_reads, I normally change it to 96 to start with, but
it will depend on size of your nodes.

Otherwise it might be badly designed queries, have you investigated which queries are producing
the client timeouts?


Paul Chandler 

> On 9 Apr 2019, at 18:58, Abdul Patel <> wrote:
> Hi,
> My nodetool tpstats arw showing all time blocked high numbers a d also read dropped messages
as 400 .
> Client is expeirince high timeouts.
> Checked few online forums they recommend to increase, native_transport_max_threads.
> As of jow its commented with 128 ..
> Is it adviabke to increase this and also can this fix timeout issue?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message