You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2018/02/08 14:24:00 UTC

[jira] [Updated] (KAFKA-4203) Java producer default max message size does not align with broker default

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

Damian Guy updated KAFKA-4203:
------------------------------
    Fix Version/s:     (was: 1.1.0)
                   2.0.0

> Java producer default max message size does not align with broker default
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-4203
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4203
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.1
>            Reporter: Grant Henke
>            Assignee: Ismael Juma
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The Java producer sets max.request.size = 1048576 (the base 2 version of 1 MB (MiB))
> The broker sets max.message.bytes = 1000012 (the base 10 value of 1 MB + 12 bytes for overhead)
> This means that by default the producer can try to produce messages larger than the broker will accept resulting in RecordTooLargeExceptions.
> There were not similar issues in the old producer because it sets max.message.size = 1000000 (the base 10 value of 1 MB)
> I propose we increase the broker default for max.message.bytes to 1048588 (the base 2 value of 1 MB (MiB) + 12 bytes for overhead) so that any message produced with default configs from either producer does not result in a RecordTooLargeException.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)