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

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

GitHub user wiyu opened a pull request:

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

    KAFKA-3937: Kafka Clients Leak Native Memory For Longer Than Needed With 
Compressed Messages

    @ijuma - Making the change against trunk based on your suggestions to have 
the stream closing handled in the private RecordIterator constructor which I 
understand is only to be used only if the block of message(s) are compressed. 


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

    $ git pull https://github.com/wiyu/kafka compressor_memory_leak_in_fetcher

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

    https://github.com/apache/kafka/pull/1760.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 #1760
    
----
commit 56451a38399875ae9d1ccdb2f873de88eae6f940
Author: William Yu <w...@unified.com>
Date:   2016-08-18T17:25:10Z

    KAFKA-3937: Kafka Clients Leak Native Memory For Longer Than Needed With 
Compressed Messages

----


> Kafka Clients Leak Native Memory For Longer Than Needed With Compressed 
> Messages
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-3937
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3937
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.8.2.2, 0.9.0.1, 0.10.0.0
>         Environment: Linux, latest oracle java-8
>            Reporter: Tom Crayford
>            Priority: Minor
>
> In https://issues.apache.org/jira/browse/KAFKA-3933, we discovered that 
> brokers can crash when performing log recovery, as they leak native memory 
> whilst decompressing compressed segments, and that native memory isn't 
> cleaned up rapidly enough by garbage collection and finalizers. The work to 
> fix that in the brokers is taking part in 
> https://github.com/apache/kafka/pull/1598. As part of that PR, Ismael Juma 
> asked me to fix similar issues in the client. Rather than have one large PR 
> that fixes everything, I'd rather break this work up into seperate things, so 
> I'm filing this JIRA to track the followup work. I should get to a PR on this 
> at some point relatively soon, once the other PR has landed.



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

Reply via email to