You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2019/02/12 10:34:01 UTC

[jira] [Resolved] (PARQUET-1485) Snappy Decompressor/Compressor may cause direct memory leak

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

Gabor Szadovszky resolved PARQUET-1485.
---------------------------------------
    Resolution: Fixed

> Snappy Decompressor/Compressor may cause direct memory leak
> -----------------------------------------------------------
>
>                 Key: PARQUET-1485
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1485
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-mr
>    Affects Versions: 1.8.1
>         Environment: parquet-1.8.1
> spark2.1
>            Reporter: liupengcheng
>            Assignee: liupengcheng
>            Priority: Major
>              Labels: pull-request-available
>
> In out production environment, we encountered a direct memory oom issues caused by the direct buffer not released in time.
> After carefully checked the code, it seems that the some methods of SnappyDecompressor/SnappyCompressor would not release the direct buffer manually. If too much direct memory allocated and no GC happens, this bug may result in direct memory oom.
> Moreover, if the `-XX:+DisableImplicitGC` jvm option is specified, the direct memory oom would happen easily for large datasets.
> Seems that the problem still exist in the latest code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)