[
https://issues.apache.org/jira/browse/KAFKA-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405223#comment-15405223
]
ASF GitHub Bot commented on KAFKA-3999:
---------------------------------------
GitHub user vahidhashemian reopened a pull request:
https://github.com/apache/kafka/pull/1698
KAFKA-3999: Record raw size of fetch responses
Currently, only the decompressed size of fetch responses is recorded. This
PR adds a sensor to keep track of the raw size as well.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka KAFKA-3999
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1698.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 #1698
----
commit ae9b0abf60e20923761eda7d5f351625a2b2c0dc
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date: 2016-08-02T23:07:27Z
KAFKA-3999: Record raw size of fetch responses
Currently, only the decompressed size of fetch responses is recorded. This
PR adds a sensor to keep track of their raw size as well.
----
> Consumer bytes-fetched metric uses decompressed message size
> ------------------------------------------------------------
>
> Key: KAFKA-3999
> URL: https://issues.apache.org/jira/browse/KAFKA-3999
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.9.0.1, 0.10.0.0
> Reporter: Jason Gustafson
> Assignee: Vahid Hashemian
> Priority: Minor
>
> It looks like the computation for the bytes-fetched metrics uses the size of
> the decompressed message set. I would have expected it to be based off of the
> raw size of the fetch responses. Perhaps it would be helpful to expose both
> the raw and decompressed fetch sizes?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
