cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject Re: Routine nodetool repair
Date Thu, 22 Dec 2011 09:09:29 GMT
The ring is balanced and the difference is pretty small. 

One other thing to consider is are you creating a few very large rows ? You can check the
min, max and average row size using nodetool cfstats. 

If all is fine don't worry about it. If you want to see the numbers get closer nodetool compact
will probably do it, but it's not something you would normally do on a production cluster.

Hope that helps. 

Aaron Morton
Freelance Developer

On 22/12/2011, at 5:18 PM, Peter Schuller wrote:

>> Could the lack of routine repair be why nodetool ring reports: node(1) Load
>> -> 78.24 MB and node(2) Load -> 67.21 MB? The load span between the two
>> nodes has been increasing ever so slowly...
> No.
> Generally there will be a variation in load depending on what state
> compaction happens to be in on the given node (I am assuming you're
> not using leveled compaction). That is in addition to any imbalance
> that might result from your population of data in the cluster.
> Running repair can affect the live size, but *lack* of repair won't
> cause a live size divergence.
> -- 
> / Peter Schuller (@scode,

View raw message