cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1746) Cleanups should be less impacting
Date Mon, 15 Nov 2010 17:38:13 GMT


Jonathan Ellis commented on CASSANDRA-1746:

The reason cleanup and compaction are different things is that rows that do not belong to
the current node can be generated by CL.ANY writes as well as "left behind" by token changes.

> Cleanups should be less impacting
> ---------------------------------
>                 Key: CASSANDRA-1746
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>            Priority: Minor
> When a new node is added its neighbours require cleanup. Cleanup is very performance
impacting and for larger data sets takes a long time. You really do not get all the benefits
of the new node until the neighbours are cleaned up.
> Suggestion:
> Configuration option that can be changed from JMX compaction_auto_cleanup := {true,false}
set to false by default.
> During non major compaction if compaction_auto_cleanup flag is set to TRUE, we look at
the natural endpoints for the key we are compacting. If the key does not belong on this machine
we can remove it. 
> This would save us from the heavy hammer of cleanup compaction. It would also be less
book keeping for administrators.  
> Most people would want to leave this at false, join new node, wait a few days. If the
node has not failed by now, it likely will not. Set the flag to true and cleanup will happen
over time. Users can still force clean up if they wish.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message