[ 
https://issues.apache.org/jira/browse/HADOOP-12007?focusedWorklogId=793359&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-793359
 ]

ASF GitHub Bot logged work on HADOOP-12007:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Jul/22 17:44
            Start Date: 20/Jul/22 17:44
    Worklog Time Spent: 10m 
      Work Description: sunchao commented on PR #4585:
URL: https://github.com/apache/hadoop/pull/4585#issuecomment-1190572837

   > @sunchao Should I create a new Jira ticket for this?
   
   @kevins-29 , yes please create a new JIRA for this issue, and change the PR 
title afterwards. Thanks.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 793359)
    Time Spent: 2h 50m  (was: 2h 40m)

> GzipCodec native CodecPool leaks memory
> ---------------------------------------
>
>                 Key: HADOOP-12007
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12007
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Yejun Yang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> org/apache/hadoop/io/compress/GzipCodec.java call 
> CompressionCodec.Util.createOutputStreamWithCodecPool to use CodecPool. But 
> compressor objects are actually never returned to pool which cause memory 
> leak.
> HADOOP-10591 uses CompressionOutputStream.close() to return Compressor object 
> to pool. But CompressionCodec.Util.createOutputStreamWithCodecPool actually 
> returns a CompressorStream which overrides close().
> This cause CodecPool.returnCompressor never being called. In my log file I 
> can see lots of "Got brand-new compressor [.gz]" but no "Got recycled 
> compressor".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to