cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Wille <>
Subject Re: Recommissioned node is much smaller
Date Wed, 03 Dec 2014 18:10:03 GMT
Load and ownership didn’t correlate nearly as well as I expected. I have lots and lots of
very small records. I would expect very high correlation.

I think the moral of the story is that I shouldn’t delete the system directory. If I have
issues with a node, I should recommission it properly.


On Dec 3, 2014, at 10:23 AM, Eric Stevens <<>>

How does the difference in load compare to the effective ownership?  If you deleted the system
directory as well, you should end up with new ranges, so I'm wondering if perhaps you just
ended up with a really bad shuffle. Did you run removenode on the old host after you took
it down (I assume so since all nodes are in UN status)?  Is the test node in its own seeds

On Tue Dec 02 2014 at 4:10:10 PM Robert Wille <<>>
I didn’t do anything except kill the server process, delete /var/lib/cassandra, and start
it back up again. nodetool status shows all nodes as UN, and doesn’t display any unexpected

I don’t know if this sheds any light on the issue, but I’ve added a considerable amount
of data to the cluster since I did the aforementioned test. The difference in size between
the nodes is shrinking. The other nodes are growing more slowly than the one I recommissioned.
That was definitely not something that I expected, and I don’t have any explanation for
that either.


On Dec 2, 2014, at 3:38 PM, Tyler Hobbs <<>>

On Tue, Dec 2, 2014 at 2:21 PM, Robert Wille <<>>
As a a test, I took down a node, deleted /var/lib/cassandra and restarted it.

Did you decommission or removenode it when you took it down?  If you didn't, the "old" node
is still in the ring, and affects the replication.

Tyler Hobbs

View raw message