You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/12/09 15:04:59 UTC

[jira] [Updated] (KAFKA-4286) metric reporter may hit NullPointerException during shutdown

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

Ismael Juma updated KAFKA-4286:
-------------------------------
    Fix Version/s: 0.10.2.0

> metric reporter may hit NullPointerException during shutdown
> ------------------------------------------------------------
>
>                 Key: KAFKA-4286
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4286
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.10.0.0
>            Reporter: Jun Rao
>            Assignee: Xavier Léauté
>             Fix For: 0.10.2.0
>
>
> When we shut down a broker, our metric reporter could throw the following exception.
> java.lang.NullPointerException
> 	at kafka.network.Processor$$anon$2.value(SocketServer.scala:392)
> 	at kafka.network.Processor$$anon$2.value(SocketServer.scala:390)
> This is because we report Yammer metric like the following and we de-register the underlying Kafka metric when shutting down the socket server.
>   newGauge("IdlePercent",
>     new Gauge[Double] {
>       def value = {
>         metrics.metrics().get(metrics.metricName("io-wait-ratio", "socket-server-metrics", metricTags)).value()
>       }
>     },
>     metricTags.asScala
>   )



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)