You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Stanislav Kozlovski (Jira)" <ji...@apache.org> on 2020/02/27 15:42:00 UTC

[jira] [Created] (KAFKA-9617) Replica Fetcher can mark partition as failed when max.message.bytes is changed

Stanislav Kozlovski created KAFKA-9617:
------------------------------------------

             Summary: Replica Fetcher can mark partition as failed when max.message.bytes is changed
                 Key: KAFKA-9617
                 URL: https://issues.apache.org/jira/browse/KAFKA-9617
             Project: Kafka
          Issue Type: Bug
            Reporter: Stanislav Kozlovski
            Assignee: Stanislav Kozlovski


There exists a race condition when changing the dynamic max.message.bytes config for a topic. A follower replica can replicate a message that is over that size after it processes the config change. When this happens, the replica fetcher catches the unexpected exception, marks the partition as failed and stops replicating it.
{code:java}
06:38:46.596	Processing override for entityPath: topics/partition-1 with config: Map(max.message.bytes -> 512)

06:38:46.597	 [ReplicaFetcher replicaId=1, leaderId=3, fetcherId=0] Unexpected error occurred while processing data for partition partition-1 at offset 20964
org.apache.kafka.common.errors.RecordTooLargeException: The record batch size in the append to partition-1 is 3349 bytes which exceeds the maximum configured value of 512.
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)