You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by feifei hsu <ea...@gmail.com> on 2016/09/14 08:21:13 UTC

KAFKA-3933: Kafka OOM During Log Recovery Due to Leaked Native Memory

Hi Tom and Ismael.
   I am following the  kafka-3933. the memory leak. but I did not see the
pr #1598 #1614 #1660 are merged into the trunk.
Do you know what the current status?
  So many thanks.
   We are also thinking backport it to 0.9.0.1

--easy

Re: KAFKA-3933: Kafka OOM During Log Recovery Due to Leaked Native Memory

Posted by feifei hsu <ea...@gmail.com>.
Hi, Ismael
   So many thanks for the quick reply
   I checked the trunk tree at github, I did not see the merge.
   did I make some mistake? sorry for that.

for example, the pull 1598. file related to the LogSegment.scala. the one
of the PR add try catch to close the leaking resource. but I did not see
the code is at trunk. :-(

https://github.com/heroku/kafka/blob/trunk/core/src/main/scala/kafka/log/LogSegment.scala#L189
https://github.com/apache/kafka/pull/1598/files#r70071062


On Wed, Sep 14, 2016 at 5:06 AM, Ismael Juma <ml...@juma.me.uk> wrote:

> Hi,
>
> We did merge the PR to trunk and 0.10.0.
>
> Ismael
>
> On Wed, Sep 14, 2016 at 9:21 AM, feifei hsu <ea...@gmail.com> wrote:
>
>> Hi Tom and Ismael.
>>    I am following the  kafka-3933. the memory leak. but I did not see the
>> pr #1598 #1614 #1660 are merged into the trunk.
>> Do you know what the current status?
>>   So many thanks.
>>    We are also thinking backport it to 0.9.0.1
>>
>> --easy
>>
>
>

Re: KAFKA-3933: Kafka OOM During Log Recovery Due to Leaked Native Memory

Posted by Ismael Juma <ml...@juma.me.uk>.
Hi,

We did merge the PR to trunk and 0.10.0.

Ismael

On Wed, Sep 14, 2016 at 9:21 AM, feifei hsu <ea...@gmail.com> wrote:

> Hi Tom and Ismael.
>    I am following the  kafka-3933. the memory leak. but I did not see the
> pr #1598 #1614 #1660 are merged into the trunk.
> Do you know what the current status?
>   So many thanks.
>    We are also thinking backport it to 0.9.0.1
>
> --easy
>