[
https://issues.apache.org/jira/browse/CASSANDRA-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932129#action_12932129
]
Edward Capriolo commented on CASSANDRA-1746:
--------------------------------------------
http://wiki.apache.org/cassandra/HintedHandoff. It is unclear (to me) if and
how CL.ANY rows get removed. Does it make sense that if a hint is being saved
on a non-replica node it should be deleted after the hint is delivered? Should
that be another issue?
Can we work around CL.ANY with addition to the logic:
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 AND THE KEY IS NOT PRESENT IN A HINT TABLE we can
remove it.
> Cleanups should be less impacting
> ---------------------------------
>
> Key: CASSANDRA-1746
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1746
> 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.
