[
https://issues.apache.org/jira/browse/CASSANDRA-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-1673:
----------------------------------------
Attachment: 0001-Expose-GcGrace-through-JMX.patch
Attaching patch to expose gcGrace through JMX (for major and user defined
compactions).
This will affect expired columns, but I don't think this is a problem.
This does not expose it through nodetool though because I'm not sure we should.
Making it an optional argument to compact is a pain because the way nodetool
parse command line arguments is fairly rigid. We could add a removeTombstone
command, that would trigger a compaction with gcGrace=0, but overall it's a
fairly dangerous operation so it doesn't seem too bad an idea to keep that
fairly hidden. Happy to add it though if people thinks it's wise.
> Add a way to force remove tombstones before GCGraceSeconds
> ----------------------------------------------------------
>
> Key: CASSANDRA-1673
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1673
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: T Jake Luciani
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 0.7.3
>
> Attachments: 0001-Expose-GcGrace-through-JMX.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> In some circumstances it might be useful to be able to force delete
> tombstones before GCGraceSeconds has elapsed.
> Example, If you know your cluster is consistent and you want to free up space.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
