changed since it started happening?
Kenneth Brotman
From: Subroto Barua [mailto:sbarua...@yahoo.com.INVALID]
Sent: Friday, February 01, 2019 10:13 AM
To: user@cassandra.apache.org
Subject: Re: Help with sudden spike in read requests
Vnode is 256
C*: 3.0.15 on m4.4xlarge gp2 vol
; happening? What changed since it started happening?
>
> Kenneth Brotman
>
> From: Subroto Barua [mailto:sbarua...@yahoo.com.INVALID]
> Sent: Friday, February 01, 2019 10:13 AM
> To: user@cassandra.apache.org
> Subject: Re: Help with sudden spike in read requests
>
>
, February 01, 2019 10:13 AM
To: user@cassandra.apache.org
Subject: Re: Help with sudden spike in read requests
Vnode is 256
C*: 3.0.15 on m4.4xlarge gp2 vol
There are 2 more DCs on bare metal (raid 10 and older machines) attached to
this cluster and we have not seen this behavior on on-prem
Vnode is 256
C*: 3.0.15 on m4.4xlarge gp2 vol
There are 2 more DCs on bare metal (raid 10 and older machines) attached to
this cluster and we have not seen this behavior on on-prem servers
If this event is triggered by some bad query/queries, what is the best way to
trap it?
Subroto
> On
If you had a query that went across the partitions and especially if you had
vNodes set high, that would do it.
Kenneth Brotman
From: Subroto Barua [mailto:sbarua...@yahoo.com.INVALID]
Sent: Friday, February 01, 2019 8:45 AM
To: User cassandra.apache.org
Subject: Help with sudden spike
