You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2011/02/05 04:03:31 UTC

[jira] Created: (CASSANDRA-2113) corrupt commitlogs can prevent C* from starting

corrupt commitlogs can prevent C* from starting
-----------------------------------------------

                 Key: CASSANDRA-2113
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2113
             Project: Cassandra
          Issue Type: Bug
            Reporter: Matthew F. Dennis
            Assignee: Matthew F. Dennis


CASSANDRA-2076 claims that a corrupt commit log prevented C* from starting.  While the reason for this corruption is a bug in it's own right, C* should not bail on boot because of a corrupted commit log.

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

        

[jira] Updated: (CASSANDRA-2113) corrupt commitlogs can prevent C* from starting

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

Matthew F. Dennis updated CASSANDRA-2113:
-----------------------------------------

    Attachment: 2113-cassandra-0.7.txt

attached patch logs unexpected exceptions during commit log replay and continues to start C*

> corrupt commitlogs can prevent C* from starting
> -----------------------------------------------
>
>                 Key: CASSANDRA-2113
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2113
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Matthew F. Dennis
>            Assignee: Matthew F. Dennis
>             Fix For: 0.7.2
>
>         Attachments: 2113-cassandra-0.7.txt
>
>
> CASSANDRA-2076 claims that a corrupt commit log prevented C* from starting.  While the reason for this corruption is a bug in it's own right, C* should not fail to start because of a corrupted commit log.

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

        

[jira] Updated: (CASSANDRA-2113) corrupt commitlogs can prevent C* from starting

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

Matthew F. Dennis updated CASSANDRA-2113:
-----------------------------------------

    Description: 
CASSANDRA-2076 claims that a corrupt commit log prevented C* from starting.  While the reason for this corruption is a bug in it's own right, C* should not fail to start because of a corrupted commit log.


  was:CASSANDRA-2076 claims that a corrupt commit log prevented C* from starting.  While the reason for this corruption is a bug in it's own right, C* should not bail on boot because of a corrupted commit log.


> corrupt commitlogs can prevent C* from starting
> -----------------------------------------------
>
>                 Key: CASSANDRA-2113
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2113
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Matthew F. Dennis
>            Assignee: Matthew F. Dennis
>
> CASSANDRA-2076 claims that a corrupt commit log prevented C* from starting.  While the reason for this corruption is a bug in it's own right, C* should not fail to start because of a corrupted commit log.

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