Re: High load on few nodes in a DC.

Yes we are using token aware but not shuffling replicas. On Wed, Sep 21, 2016 at 10:04 AM, Romain Hardouin wrote: > Hi, > > Do you shuffle the replicas with TokenAwarePolicy? > TokenAwarePolicy(LoadBalancingPolicy childPolicy, boolean > shuffleReplicas) > > Best, > > Romain

Re: High load on few nodes in a DC.

Hi, Do you shuffle the replicas with TokenAwarePolicy?TokenAwarePolicy(LoadBalancingPolicy childPolicy, boolean shuffleReplicas)  Best, RomainLe Mardi 20 septembre 2016 15h47, Pranay akula a écrit : I was a able to find the hotspots causing the load,but the

Re: High load on few nodes in a DC.

I was a able to find the hotspots causing the load,but the size of these partitions are in KB and no tombstones and no.of sstables is only 2 what else i need to debug to find the reason for high load for some nodes. we are also using unlogged batches is that can be the reason ?? how to find

Re: High load on few nodes in a DC.

I was able to see most used partitions but the nodes with less load are serving more read and write requests for that particular partitions when compared to nodes with high load, how can i find if these nodes are serving as co-coordinators for those read and write requests ?? how can i find the

Re: High load on few nodes in a DC.

Hai Jeff, Thank, we are using RF 3 and cassandra version 2.1.8. Thanks Pranay. On Mon, Sep 19, 2016 at 10:55 AM, Jeff Jirsa wrote: > Is your replication_factor 2? Or is it 3? What version are you using? > > > > The most likely answer is some individual partition

Re: High load on few nodes in a DC.

Is your replication_factor 2? Or is it 3?  What version are you using? The most likely answer is some individual partition that’s either being written/read more than others, or is somehow impacting the cluster (wide rows are a natural candidate). You don’t mention your version, but most