You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/19 07:28:25 UTC

[jira] [Commented] (KAFKA-3580) improve error logging in ReplicaFetchThread with oversized message

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

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

GitHub user omkreddy opened a pull request:

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

    KAFKA-3580; improve error logging in ReplicaFetchThread

    

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

    $ git pull https://github.com/omkreddy/kafka KAFKA-3580

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

    https://github.com/apache/kafka/pull/1237.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 #1237
    
----
commit 56bf00ce345bb95ca2122e4c1feeb313b0867dff
Author: Manikumar reddy O <ma...@gmail.com>
Date:   2016-04-19T05:22:40Z

    KAFKA-3580; improve error logging in ReplicaFetchThread

----


> improve error logging in ReplicaFetchThread with oversized message
> ------------------------------------------------------------------
>
>                 Key: KAFKA-3580
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3580
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.9.0.1
>            Reporter: Jun Rao
>              Labels: label
>
> Currently, the follower will log the following if it encounters an oversized message. It would be useful to include the affected topic/partition in the log.
> Replication is failing due to a message that is greater than replica.fetch.max.bytes. This " +
>         "generally occurs when the max.message.bytes has been overridden to exceed this value and a suitably large " +
>         "message has also been sent. To fix this problem increase replica.fetch.max.bytes in your broker config to be " +
>         "equal or larger than your settings for max.message.bytes, both at a broker and topic level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)