kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiangjie Qin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6264) Log cleaner thread may die on legacy segment containing messages whose offsets are too large
Date Wed, 29 Nov 2017 01:08:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269853#comment-16269853

Jiangjie Qin commented on KAFKA-6264:

[~hachikuji] Yes, that may be a workaround. If the first message was the problem. One corner
case is that if the segment is the first segment, i.e. 000000000000000.log, in addition to
change the segment name to use the first offset of the message, we need to add an empty log
segment at 000000000000000.log, otherwise the log starting offset will change.

> Log cleaner thread may die on legacy segment containing messages whose offsets are too
> --------------------------------------------------------------------------------------------
>                 Key: KAFKA-6264
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6264
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions:, 1.0.0,
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>            Priority: Critical
>             Fix For: 1.0.1
> We encountered a problem that some of the legacy log segments contains messages whose
offsets are larger than {{SegmentBaseOffset + Int.MaxValue}}.
> Prior to, we do not assert the offset of the messages when appending them to
the log segments. Due to KAFKA-5413, the log cleaner may append messages whose offset is greater
than {{base_offset + Int.MaxValue}} into the segment during the log compaction.
> After the brokers are upgraded, those log segments cannot be compacted anymore because
the compaction will fail immediately due to the offset range assertion we added to the LogSegment.
> We have seen this issue in the __consumer_offsets topic so it could be a general problem.
There is no easy solution for the users to recover from this case. 
> One solution is to split such log segments in the log cleaner once it sees a message
with problematic offset and append those messages to a separate log segment with a larger
> Due to the impact of the issue. We may want to consider backporting the fix to previous
affected versions.

This message was sent by Atlassian JIRA

View raw message