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

Posted to dev@kafka.apache.org by "Dong Lin (JIRA)" <ji...@apache.org> on 2015/06/03 22:26:38 UTC

[jira] [Updated] (KAFKA-1936) Track offset commit requests separately from produce requests

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

Dong Lin updated KAFKA-1936:
----------------------------
    Resolution: Not A Problem
        Status: Resolved  (was: Patch Available)

After discussion we decided to keep internal topic data as part of BrokerTopicStats.

> Track offset commit requests separately from produce requests
> -------------------------------------------------------------
>
>                 Key: KAFKA-1936
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1936
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Aditya Auradkar
>            Assignee: Dong Lin
>         Attachments: KAFKA-1936.patch, KAFKA-1936_2015-04-26_21:20:28.patch, KAFKA-1936_2015-04-26_21:26:34.patch, KAFKA-1936_2015-05-04_15:17:50.patch, KAFKA-1936_2015-05-12_07:32:07.patch, KAFKA-1936_2015-05-12_08:02:32.patch
>
>
> In ReplicaManager, failed and total produce requests are updated from appendToLocalLog. Since offset commit requests also follow the same path, they are counted along with produce requests. Add a metric and count them separately.



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