kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4203) Java producer default max message size does not align with broker default
Date Sat, 28 Oct 2017 15:48:00 GMT

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

ASF GitHub Bot commented on KAFKA-4203:
---------------------------------------

GitHub user ijuma opened a pull request:

    https://github.com/apache/kafka/pull/4154

    KAFKA-4203: Align broker default for max.message.bytes with Java producer default

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ijuma/kafka kafka-4203-align-broker-max-message-bytes-with-java-producer

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/4154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4154
    
----
commit 15cf53bf2643bd0ea164d70f76e36acdd65d0990
Author: Ismael Juma <ismael@juma.me.uk>
Date:   2017-10-28T15:46:44Z

    KAFKA-4203: Align broker default for max.message.bytes with Java producer default

----


> 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: Grant Henke
>            Priority: Critical
>             Fix For: 1.1.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
(v6.4.14#64029)

Mime
View raw message