kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Picka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler
Date Mon, 12 Oct 2015 11:54:05 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953030#comment-14953030
] 

Vladimir Picka commented on KAFKA-1804:
---------------------------------------

Hello, I just would like to report that this error was thrown after 4 days run on Kafka version:
kafka-0.8.2.2-2.11. Unfortunately we were not able to reproduce the error yet. I just want
to increase the attention to this issue.

{code}
[2015-10-08 14:40:47,176] ERROR Uncaught exception in thread 'kafka-network-thread-9092-1':
(kafka.utils.Utils$)
java.util.NoSuchElementException: None.get
        at scala.None$.get(Option.scala:347)
        at scala.None$.get(Option.scala:345)
        at kafka.network.ConnectionQuotas.dec(SocketServer.scala:524)
        at kafka.network.AbstractServerThread.close(SocketServer.scala:165)
        at kafka.network.AbstractServerThread.close(SocketServer.scala:157)
        at kafka.network.Processor.close(SocketServer.scala:374)
        at kafka.network.Processor.processNewResponses(SocketServer.scala:406)
        at kafka.network.Processor.run(SocketServer.scala:318)
        at java.lang.Thread.run(Thread.java:745)
[2015-10-08 14:40:47,177] INFO Closing socket connection to /10.33.167.154. (kafka.network.Processor)
[2015-10-08 14:40:47,177] INFO Closing socket connection to /10.33.167.154. (kafka.network.Processor)
[2015-10-08 14:40:47,177] INFO Closing socket connection to /10.33.167.154. (kafka.network.Processor)
[2015-10-08 14:40:47,177] ERROR Uncaught exception in thread 'kafka-network-thread-9092-0':
(kafka.utils.Utils$)
java.util.NoSuchElementException: None.get
        at scala.None$.get(Option.scala:347)
        at scala.None$.get(Option.scala:345)
        at kafka.network.ConnectionQuotas.dec(SocketServer.scala:524)
        at kafka.network.AbstractServerThread.close(SocketServer.scala:165)
        at kafka.network.AbstractServerThread.close(SocketServer.scala:157)
        at kafka.network.Processor.close(SocketServer.scala:374)
        at kafka.network.Processor.run(SocketServer.scala:350)
        at java.lang.Thread.run(Thread.java:745)
{code}

> Kafka network thread lacks top exception handler
> ------------------------------------------------
>
>                 Key: KAFKA-1804
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1804
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.2.0
>            Reporter: Oleg Golovin
>            Priority: Critical
>
> We have faced the problem that some kafka network threads may fail, so that jstack attached
to Kafka process showed fewer threads than we had defined in our Kafka configuration. This
leads to API requests processed by this thread getting stuck unresponed.
> There were no error messages in the log regarding thread failure.
> We have examined Kafka code to find out there is no top try-catch block in the network
thread code, which could at least log possible errors.
> Could you add top-level try-catch block for the network thread, which should recover
network thread in case of exception?



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

Mime
View raw message