You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dhruvil Shah (JIRA)" <ji...@apache.org> on 2018/09/07 15:32:00 UTC
[jira] [Updated] (KAFKA-7385) Log compactor crashes when empty
headers are retained with idempotent or transactional producers
[ https://issues.apache.org/jira/browse/KAFKA-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dhruvil Shah updated KAFKA-7385:
--------------------------------
Summary: Log compactor crashes when empty headers are retained with idempotent or transactional producers (was: Log compactor crashes when empty headers are retained with idempotent / transaction producers)
> Log compactor crashes when empty headers are retained with idempotent or transactional producers
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-7385
> URL: https://issues.apache.org/jira/browse/KAFKA-7385
> Project: Kafka
> Issue Type: Bug
> Reporter: Dhruvil Shah
> Priority: Major
>
> During log compaction, we retain an empty header if the batch contains the last sequence number for a particular producer. When such headers are the only messages retained, we do not update state such as `maxOffset` in `MemoryRecords#filterTo` causing us to append these into the cleaned segment with `largestOffset` = -1. This throws a `LogSegmentOffsetOverflowException` for a segment that does not actually have an overflow. When we attempt to split the segment, the log cleaner dies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)