You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Onur Karaman (JIRA)" <ji...@apache.org> on 2016/07/28 18:53:20 UTC

[jira] [Resolved] (KAFKA-4004) NetworkReceive.complete() should not throw NullPointerException after partially reading the size

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

Onur Karaman resolved KAFKA-4004.
---------------------------------
    Resolution: Not A Bug

Okay yeah the code is doing the right thing. I missed an earlier OutOfMemoryError called during
{code}
this.buffer = ByteBuffer.allocate(receiveSize);
{code}

MirrorMaker swallows all throwables at some point in the code, so the next time we try to KafkaChannel.read, the buffer will be null while !size.hasRemaining().

Basically this boils down to me trying to mirror too much from too few MirrorMakers.

> NetworkReceive.complete() should not throw NullPointerException after partially reading the size
> ------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-4004
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4004
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Onur Karaman
>            Assignee: Onur Karaman
>
> NetworkReceive.readFrom can partially read the size and not allocate a buffer. A following NetworkReceive.complete() should not throw a NullPointerException and should instead just return false.



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