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

Posted to jira@kafka.apache.org by "Vahid Hashemian (JIRA)" <ji...@apache.org> on 2018/07/10 23:55:00 UTC

[jira] [Updated] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size (KIP-264)

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

Vahid Hashemian updated KAFKA-3999:
-----------------------------------
    Summary: Consumer bytes-fetched metric uses decompressed message size (KIP-264)  (was: Consumer bytes-fetched metric uses decompressed message size)

> 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
>             Fix For: 2.1.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)