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

Posted to dev@kafka.apache.org by "Joel Koshy (JIRA)" <ji...@apache.org> on 2015/02/18 02:37:12 UTC

[jira] [Resolved] (KAFKA-1943) Producer request failure rate should not include MessageSetSizeTooLarge and MessageSizeTooLargeException

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

Joel Koshy resolved KAFKA-1943.
-------------------------------
    Resolution: Fixed

Committed to trunk

> Producer request failure rate should not include MessageSetSizeTooLarge and MessageSizeTooLargeException
> --------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-1943
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1943
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Aditya A Auradkar
>            Assignee: Aditya Auradkar
>         Attachments: KAFKA-1943.patch
>
>
> If MessageSetSizeTooLargeException or MessageSizeTooLargeException is thrown from Log, then ReplicaManager counts it as a failed produce request. My understanding is that this metric should only count failures as a result of broker issues and not bad requests sent by the clients.
> If the message or message set is too large, then it is a client side error and should not be reported. (similar to NotLeaderForPartitionException, UnknownTopicOrPartitionException).



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