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

ASF GitHub Bot commented on KAFKA-5587:
---------------------------------------

GitHub user rajinisivaram opened a pull request:

    https://github.com/apache/kafka/pull/3526

    KAFKA-5587: Remove channel only after staged receives are delivered

    When idle connections are closed, ensure that channels with staged receives 
are retained in `closingChannels` until all staged receives are completed. Also 
ensure that only one staged receive is completed in each poll, even when 
channels are closed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rajinisivaram/kafka KAFKA-5587

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3526.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3526
    
----
commit d6848a3b1dcf9cc73caf06b68bdc89570c396c81
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date:   2017-07-14T08:36:22Z

    KAFKA-5587: Remove channel only after staged receives are delivered

----


> Processor got uncaught exception: NullPointerException
> ------------------------------------------------------
>
>                 Key: KAFKA-5587
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5587
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.10.1.1
>            Reporter: Dan
>            Assignee: Rajini Sivaram
>
> [2017-07-12 21:56:39,964] ERROR Processor got uncaught exception. 
> (kafka.network.Processor)
> java.lang.NullPointerException
>         at 
> kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:490)
>         at 
> kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:487)
>         at scala.collection.Iterator$class.foreach(Iterator.scala:727)
>         at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
>         at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
>         at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
>         at 
> kafka.network.Processor.processCompletedReceives(SocketServer.scala:487)
>         at kafka.network.Processor.run(SocketServer.scala:417)
>         at java.lang.Thread.run(Thread.java:745)
> Anyone knows the cause of this exception? What's the effect of it? 
> When this exception occurred, the log also showed that the broker was 
> frequently shrinking ISR to itself. Are these two things interrelated?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to