You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/26 21:16:20 UTC
[jira] [Commented] (KAFKA-3999) Consumer bytes-fetched metric uses
decompressed message size
[ https://issues.apache.org/jira/browse/KAFKA-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15524193#comment-15524193 ]
ASF GitHub Bot commented on KAFKA-3999:
---------------------------------------
Github user vahidhashemian closed the pull request at:
https://github.com/apache/kafka/pull/1698
> 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)