cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13918) Header only commit logs should be filtered before recovery
Date Fri, 29 Sep 2017 18:09:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Tunnicliffe updated CASSANDRA-13918:
----------------------------------------
    Status: Ready to Commit  (was: Patch Available)

> Header only commit logs should be filtered before recovery
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-13918
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13918
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>             Fix For: 3.0.15, 4.0, 3.11.x
>
>
> Commit log recovery will tolerate commit log truncation in the most recent log file found
on disk, but will abort startup if problems are detected in others. 
> Since we allocate commit log segments before they're used though, it's possible to get
into a state where the last commit log file actually written to is not the same file that
was most recently allocated, preventing startup for what should otherwise be allowable incomplete
final segments.
> Excluding header only files on recovery should prevent this from happening.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message