You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Aditya A Auradkar (JIRA)" <ji...@apache.org> on 2015/02/10 23:17:12 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14315068#comment-14315068 ] 

Aditya A Auradkar commented on KAFKA-1943:
------------------------------------------

Created reviewboard https://reviews.apache.org/r/30848/diff/
 against branch origin/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: Bug
>            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)