cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Gahire (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-3923) Cassandra Nodetool Cleanup causing sstable corruption.
Date Thu, 16 Feb 2012 06:46:59 GMT
Cassandra Nodetool Cleanup causing sstable corruption.
------------------------------------------------------

                 Key: CASSANDRA-3923
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3923
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
    Affects Versions: 0.8.2
            Reporter: Samarth Gahire
             Fix For: 1.1.0


We recently doubled size of our cluster. 
After that,we ran the cleanup on the old machines in the cluster.
After that we loaded the data which triggered minor compaction which did not complete due
to corrupt sstables
This was the case with those machines only on which we ran the cleanup.

As the cleanup is unavoidable after node addition, what is the way to avoid this problem?
Is this issue fixed in newer versions of Cassandra(As we are using cassandra-0.8.2)?

OR 

Are there any steps / procedure that will avoid need of cleanup after node addition.
The same issue is reported here: CASSANDRA-3065

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message