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

Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2014/01/17 19:28:22 UTC

[jira] [Commented] (KAFKA-1055) BrokerTopicStats is updated before checking for MessageSizeTooLarge

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

Guozhang Wang commented on KAFKA-1055:
--------------------------------------

Created reviewboard https://reviews.apache.org/r/17055/
 against branch origin/trunk

> BrokerTopicStats is updated before checking for MessageSizeTooLarge
> -------------------------------------------------------------------
>
>                 Key: KAFKA-1055
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1055
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>             Fix For: 0.8.1
>
>         Attachments: KAFKA-1055.patch
>
>
> In Log.append function, BrokerTopicStats is updated before the checking for MessageSizeTooLarge, hence even if messages are refused at the server due to this exception, their counts would still be aggregated. Need to move the BrokerTopicStats update after the checking.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)