kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-3999) Consumer bytes-fetched metric uses decompressed message size
Date Thu, 28 Sep 2017 12:24:00 GMT

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

Ismael Juma updated KAFKA-3999:
-------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0

> 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
>             Fix For: 1.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
(v6.4.14#64029)

Mime
View raw message