[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value
[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032261#comment-16032261 ] Jun Rao commented on KAFKA-4592: [~huxi], sorry for the late response. If a metric is never updated, perhaps it's better to set max to NaN? Things like rate could default to 0. > Kafka Producer Metrics Invalid Value > > > Key: KAFKA-4592 > URL: https://issues.apache.org/jira/browse/KAFKA-4592 > Project: Kafka > Issue Type: Bug > Components: core, producer >Affects Versions: 0.10.1.1 >Reporter: AJ Jwair >Assignee: huxi > > Producer metrics > Metric name: record-size-max > When no records are produced during the monitoring window, the > record-size-max has an invalid value of -9.223372036854776E16 > Please notice that the value is not a very small number close to zero bytes, > it is negative 90 quadrillion bytes > The same behavior was observed in: records-lag-max -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value
[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980818#comment-15980818 ] huxi commented on KAFKA-4592: - [~ijuma] What's the status for this jira after you said you need a discussion with Jun about whether 0 is a good initial value for metrics > Kafka Producer Metrics Invalid Value > > > Key: KAFKA-4592 > URL: https://issues.apache.org/jira/browse/KAFKA-4592 > Project: Kafka > Issue Type: Bug > Components: core, producer >Affects Versions: 0.10.1.1 >Reporter: AJ Jwair >Assignee: huxi > > Producer metrics > Metric name: record-size-max > When no records are produced during the monitoring window, the > record-size-max has an invalid value of -9.223372036854776E16 > Please notice that the value is not a very small number close to zero bytes, > it is negative 90 quadrillion bytes > The same behavior was observed in: records-lag-max -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value
[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802054#comment-15802054 ] Guozhang Wang commented on KAFKA-4592: -- @huxi Could you follow the process described here for submitting your PR? In this way it will be auto-linked to the JIRA. https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes#ContributingCodeChanges-PullRequest > Kafka Producer Metrics Invalid Value > > > Key: KAFKA-4592 > URL: https://issues.apache.org/jira/browse/KAFKA-4592 > Project: Kafka > Issue Type: Bug > Components: core, producer >Affects Versions: 0.10.1.1 >Reporter: AJ Jwair >Assignee: huxi > > Producer metrics > Metric name: record-size-max > When no records are produced during the monitoring window, the > record-size-max has an invalid value of -9.223372036854776E16 > Please notice that the value is not a very small number close to zero bytes, > it is negative 90 quadrillion bytes > The same behavior was observed in: records-lag-max -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value
[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801348#comment-15801348 ] huxi commented on KAFKA-4592: - Seems that o.a.k.common.metrics.stats.Max's default constructor assign Double.NEGATIVE_INFINITY as the initial value, but for the record size and like, value of zero is more reasonable. > Kafka Producer Metrics Invalid Value > > > Key: KAFKA-4592 > URL: https://issues.apache.org/jira/browse/KAFKA-4592 > Project: Kafka > Issue Type: Bug > Components: core, producer >Affects Versions: 0.10.1.1 >Reporter: AJ Jwair > > Producer metrics > Metric name: record-size-max > When no records are produced during the monitoring window, the > record-size-max has an invalid value of -9.223372036854776E16 > Please notice that the value is not a very small number close to zero bytes, > it is negative 90 quadrillion bytes > The same behavior was observed in: records-lag-max -- This message was sent by Atlassian JIRA (v6.3.4#6332)
