You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2011/02/23 19:59:38 UTC

[jira] Created: (CASSANDRA-2229) Back off compaction after failure

Back off compaction after failure
---------------------------------

                 Key: CASSANDRA-2229
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2229
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
    Affects Versions: 0.7.2
            Reporter: Nick Bailey
            Priority: Minor
             Fix For: 0.8


When compaction fails (for one of the multitude of reasons it can fail, generally some sort of 'corruption'), we should back off on attempting to compact that column family.  Continuously trying to compact it will just waste resources.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CASSANDRA-2229) Back off compaction after failure

Posted by "Ryan King (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998511#comment-12998511 ] 

Ryan King commented on CASSANDRA-2229:
--------------------------------------

It might be worth keeping track of the specific SSTables involved in the failed compaction and skipping those. Its possible we could make some progress on compaction in scenarios where a single sstable is corrupt.

> Back off compaction after failure
> ---------------------------------
>
>                 Key: CASSANDRA-2229
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2229
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.2
>            Reporter: Nick Bailey
>            Priority: Minor
>             Fix For: 0.8
>
>
> When compaction fails (for one of the multitude of reasons it can fail, generally some sort of 'corruption'), we should back off on attempting to compact that column family.  Continuously trying to compact it will just waste resources.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (CASSANDRA-2229) Back off compaction after failure

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-2229.
---------------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 0.8)

in progress on CASSANDRA-2261

> Back off compaction after failure
> ---------------------------------
>
>                 Key: CASSANDRA-2229
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2229
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.2
>            Reporter: Nick Bailey
>            Priority: Minor
>
> When compaction fails (for one of the multitude of reasons it can fail, generally some sort of 'corruption'), we should back off on attempting to compact that column family.  Continuously trying to compact it will just waste resources.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira