[
https://issues.apache.org/jira/browse/CASSANDRA-13918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-13918:
----------------------------------------
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed as {{95839aae2fde28fa29b16741de6bd52c0697843f}}
> 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: [email protected]
For additional commands, e-mail: [email protected]
