cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5051) Allow automatic cleanup after gc_grace
Date Sun, 07 Apr 2013 22:05:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625029#comment-13625029
] 

Edward Capriolo commented on CASSANDRA-5051:
--------------------------------------------

That is not rational that describes why cleanup is no longer required. It
is only rational that argues life would be easier if I did not have to do
it.

I agree with the argument that not having to run cleanup would be nice on
administrators.

My point was this opinion has been put forward before and been denied. I'm
not going to look up the jira, but if I were to find it and quote it, how
can we account for previous arguments against it.

https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625027#comment-13625027]
allowed?
0001-5051-with-test-fixes.patch, 0001-CASSANDRA-5051.patch,
0002-5051-remove-upgradesstable.patch,
0002-5051-remove-upgradesstable-v4.patch,
0004-5051-additional-test-v4.patch, 5051-v2.txt
all the machines, because you don't know which are affected and chances are
it was most if not all of them.  As an alternative to this intensive
process, we could allow cleanup during compaction if the data is older than
gc_grace (or perhaps some other time period since people tend to use
gc_grace hacks to get rid of tombstones.)
administrators

                
> Allow automatic cleanup after gc_grace
> --------------------------------------
>
>                 Key: CASSANDRA-5051
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5051
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Vijay
>              Labels: vnodes
>             Fix For: 2.0
>
>         Attachments: 0001-5051-v4.patch, 0001-5051-with-test-fixes.patch, 0001-CASSANDRA-5051.patch,
0002-5051-remove-upgradesstable.patch, 0002-5051-remove-upgradesstable-v4.patch, 0004-5051-additional-test-v4.patch,
5051-v2.txt
>
>
> When using vnodes, after adding a new node you have to run cleanup on all the machines,
because you don't know which are affected and chances are it was most if not all of them.
 As an alternative to this intensive process, we could allow cleanup during compaction if
the data is older than gc_grace (or perhaps some other time period since people tend to use
gc_grace hacks to get rid of tombstones.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message