[ https://issues.apache.org/jira/browse/KAFKA-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770594#comment-16770594 ]
Matthias J. Sax commented on KAFKA-3999: ---------------------------------------- Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release. > Consumer bytes-fetched metric uses decompressed message size (KIP-264) > ---------------------------------------------------------------------- > > 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 > Labels: kip > Fix For: 2.2.0 > > > 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 (v7.6.3#76005)