Re: All time blocked in nodetool tpstats

2019-04-11 Thread Paul Chandler
ave you investigated which > queries are producing the client timeouts? > > Regards > > Paul Chandler > > > > > On 9 Apr 2019, at 18:58, Abdul Patel > <mailto:abd786...@gmail.com>> wrote: > > > > Hi, > > > > My nodetool tpsta

Re: All time blocked in nodetool tpstats

2019-04-10 Thread Abdul Patel
nt_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 >>

Re: All time blocked in nodetool tpstats

2019-04-10 Thread Anthony Grasso
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 &g

All time blocked in nodetool tpstats

2019-04-10 Thread Abdul Patel
t; > Regards > > 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 time

Re: All time blocked in nodetool tpstats

2019-04-10 Thread Abdul Patel
ed queries, have you investigated which > queries are producing the client timeouts? > > Regards > > Paul Chandler > > > > > On 9 Apr 2019, at 18:58, Abdul Patel wrote: > > > > Hi, > > > > My nodetool tpstats arw showing all time blocked high numbers

Re: All time blocked in nodetool tpstats

2019-04-10 Thread Paul Chandler
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. >

Re: All time blocked in nodetool tpstats

2019-04-10 Thread Jean Carlo
9 PM 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

All time blocked in nodetool tpstats

2019-04-09 Thread Abdul Patel
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

Re: One thread pool per repair in nodetool tpstats

2017-02-21 Thread Vincent Rischmann
o Cassandra 2.2.8 and noticed something weird in nodetool >> tpstats: >> >> Pool NameActive Pending Completed >> Blocked All time blocked >> MutationStage 0 0 116265693 >> 0

Re: One thread pool per repair in nodetool tpstats

2017-02-21 Thread Matija Gobec
They appear for each repair run and disappear when repair run finishes. On Tue, Feb 21, 2017 at 11:14 AM, Vincent Rischmann wrote: > Hi, > > I upgraded to Cassandra 2.2.8 and noticed something weird in nodetool > tpstats: > > Pool NameActive Pend

One thread pool per repair in nodetool tpstats

2017-02-21 Thread Vincent Rischmann
Hi, I upgraded to Cassandra 2.2.8 and noticed something weird in nodetool tpstats: Pool NameActive Pending Completed Blocked All time blocked MutationStage 0 0 116265693 0 0 ReadStage 1

Re: nodetool tpstats

2013-09-18 Thread Tyler Hobbs
On Wed, Sep 18, 2013 at 3:43 PM, Kanwar Sangha wrote: > what does the request_response signify ? That the node accepted the > message but was not able to process it in the timeout ? > > ** > Yes, I'm pretty sure it's referring to requests that the node dropped when acting as a coordinator (d

nodetool tpstats

2013-09-18 Thread Kanwar Sangha
Hi - During a write heavy load, the tpstats show the following - Message type Dropped RANGE_SLICE 0 READ_REPAIR 0 BINARY 0 READ 0 MUTATION 65570 _TRACE 0 REQUEST_RESPONSE

Re: Large number of pending gossip stage tasks in nodetool tpstats

2013-08-07 Thread Faraaz Sareshwala
CPU we would expect to see it across the board. >> >> Cheers >> >> >> >> - >> Aaron Morton >> Cassandra Consultant >> New Zealand >> >> @aaronmorton >> http://www.thelastpickle.com >> >> On 7/08/

Re: Large number of pending gossip stage tasks in nodetool tpstats

2013-08-07 Thread Faraaz Sareshwala
; New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 7/08/2013, at 7:52 AM, Faraaz Sareshwala wrote: > >> I'm running cassandra-1.2.8 in a cluster with 45 nodes across three racks. >> All >> nodes are well behaved except one. Whenever I sta

Re: Large number of pending gossip stage tasks in nodetool tpstats

2013-08-07 Thread Aaron Morton
ss three racks. All > nodes are well behaved except one. Whenever I start this node, it starts > churning CPU. Running nodetool tpstats, I notice that the number of pending > gossip stage tasks is constantly increasing [1]. When looking at nodetool > gossipinfo, I notice that this node has

Large number of pending gossip stage tasks in nodetool tpstats

2013-08-06 Thread Faraaz Sareshwala
I'm running cassandra-1.2.8 in a cluster with 45 nodes across three racks. All nodes are well behaved except one. Whenever I start this node, it starts churning CPU. Running nodetool tpstats, I notice that the number of pending gossip stage tasks is constantly increasing [1]. When looki

Re: Regarding nodetool tpstats

2012-03-26 Thread aaron morton
Cheers :) - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 26/03/2012, at 1:55 PM, Watanabe Maki wrote: >> - InternalResponseStage > > Handles response to non client initiated messages, including bootstrap, > schema check, etc. > > maki > > > O

Re: Regarding nodetool tpstats

2012-03-25 Thread Watanabe Maki
> - InternalResponseStage Handles response to non client initiated messages, including bootstrap, schema check, etc. maki On 2012/03/26, at 2:18, aaron morton wrote: > Work is broken up into a series of stages. > > - ReadStage - performing a local read. > - RequestResponseStage - handling

Re: Regarding nodetool tpstats

2012-03-25 Thread aaron morton
Work is broken up into a series of stages. - ReadStage - performing a local read. - RequestResponseStage - handling responses from other nodes. - MutationStage - performing a local write. - ReplicateOnWriteStage - for counter writes, replicates after a local write - GossipStage - handles gossip

Regarding nodetool tpstats

2012-03-23 Thread Rishabh Agrawal
Hello I am new to Cassandra and when I run tpstats on my node (Cassandra 1.0.7) I get following output: Pool NameActive Pending Completed Blocked All time blocked ReadStage 0 0 12 0 0 RequestResp

Re: nodetool tpstats feature request

2011-08-31 Thread David Hawthorne
watch doesn't calculate diffs On Aug 31, 2011, at 2:29 PM, Peter Sanford wrote: > I use `watch` to do this: > > watch -n 5 nodetool -h localhost tpstats > > -psanford > > On Wed, Aug 31, 2011 at 1:59 PM, David Hawthorne > wrote: >> It would be very useful to be able to get refreshing statist

Re: nodetool tpstats feature request

2011-08-31 Thread Peter Sanford
I use `watch` to do this: watch -n 5 nodetool -h localhost tpstats -psanford On Wed, Aug 31, 2011 at 1:59 PM, David Hawthorne wrote: > It would be very useful to be able to get refreshing statistics from tpstats, > a la top. > > nodetool -h localhost tpstats [n] > > refresh every second, show

nodetool tpstats feature request

2011-08-31 Thread David Hawthorne
It would be very useful to be able to get refreshing statistics from tpstats, a la top. nodetool -h localhost tpstats [n] refresh every second, show me the Active and Pending and Blocked columns as they currently exist, but under Completed show me a per-second rate based on the delta from the