cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13282) Commitlog replay may fail if last mutation is within 4 bytes of end of segment
Date Thu, 09 Mar 2017 07:22:38 GMT

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

Branimir Lambov updated CASSANDRA-13282:
----------------------------------------
    Status: Ready to Commit  (was: Patch Available)

> Commitlog replay may fail if last mutation is within 4 bytes of end of segment
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13282
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13282
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>             Fix For: 2.2.x, 3.0.x, 3.11.x, 4.x
>
>         Attachments: whiteboard.png
>
>
> Following CASSANDRA-9749 , stricter correctness checks on commitlog replay can incorrectly
detect "corrupt segments" and stop commitlog replay (and potentially stop cassandra, depending
on the configured policy). In {{CommitlogReplayer#replaySyncSection}} we try to read a 4 byte
int {{serializedSize}}, and if it's 0 (which will happen due to zeroing when the segment was
created), we continue on to the next segment. However, it appears that if a mutation is sized
such that it ends with 1, 2, or 3 bytes remaining in the segment, we'll pass the {{isEOF}}
on the while loop but fail to read the {{serializedSize}} int, and fail. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message