Yes the queries are all select queries as they are more of read intensive app. Last night i rebooted cluster and today they are fine .(i know its temporary) as i still is all time blocked values. I am thinking of incresiing concurrent
On Wednesday, April 10, 2019, Paul Chandler <p...@redshots.com> wrote: > 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? > > Regards > > Paul Chandler > > > > > On 9 Apr 2019, at 18:58, Abdul Patel <abd786...@gmail.com> 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: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
