o identify a hotspot
> due to some external behavior (some partition being read thousands of
> times, over and over could certainly drive up load).
>
> - Jeff
>
> *From: *Pranay akula
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Monday, September 19
thousands of times, over and over could certainly drive up load). -
Jeff From: Pranay akula
Reply-To: "user@cassandra.apache.org"
Date: Monday, September 19, 2016 at 7:53 AM
To: "user@cassandra.apache.org"
Subject: High load on few nodes in a DC. when our cluster
ions – perhaps you can use that to identify a hotspot
>>> due to some external behavior (some partition being read thousands of
>>> times, over and over could certainly drive up load).
>>>
>>>
>>>
>>> - Jeff
>>>
>>>
>>>
>&
that to identify a hotspot
>> due to some external behavior (some partition being read thousands of
>> times, over and over could certainly drive up load).
>>
>>
>>
>> - Jeff
>>
>>
>>
>> *From: *Pranay akula
>>
quot;user@cassandra.apache.org"
> *Date: *Monday, September 19, 2016 at 7:53 AM
> *To: *"user@cassandra.apache.org"
> *Subject: *High load on few nodes in a DC.
>
>
>
> when our cluster was under load i am seeing 1 or 2 nodes are on more
> load consisten
load).
- Jeff
From: Pranay akula
Reply-To: "user@cassandra.apache.org"
Date: Monday, September 19, 2016 at 7:53 AM
To: "user@cassandra.apache.org"
Subject: High load on few nodes in a DC.
when our cluster was under load i am seeing 1 or 2 nodes are on mor
when our cluster was under load i am seeing 1 or 2 nodes are on more load
consistently when compared to others in dc i am not seeing any GC pauses or
wide partitions is this can be those nodes are continuously serving as
coordinators ?? how can i find what is the reason for high load on those
t
