[
https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801348#comment-15801348
]
huxi edited comment on KAFKA-4592 at 1/5/17 2:36 PM:
-----------------------------------------------------
Seems that o.a.k.common.metrics.stats.Max's default constructor assigns
Double.NEGATIVE_INFINITY as the initial value and picks NEGATIVE_INFINITY in
combine, but for the record size and like, value of zero is more reasonable.
was (Author: huxi_2b):
Seems that o.a.k.common.metrics.stats.Max's default constructor assigns
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
> 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)
