You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2017/07/26 21:41:00 UTC

[jira] [Resolved] (DRILL-5160) Memory leak in Parquet async reader when Snappy fails

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

Kunal Khatua resolved DRILL-5160.
---------------------------------
       Resolution: Fixed
         Assignee: Kunal Khatua  (was: Parth Chandra)
         Reviewer: Parth Chandra
    Fix Version/s: 1.11.0

Unit tests passed with the PR (https://github.com/apache/drill/pull/862) for DRILL-5420.
This JIRA might be symptomatic of that issue. The UnitTests mentioned do not fail any more. 

> Memory leak in Parquet async reader when Snappy fails
> -----------------------------------------------------
>
>                 Key: DRILL-5160
>                 URL: https://issues.apache.org/jira/browse/DRILL-5160
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.9.0
>            Reporter: Paul Rogers
>            Assignee: Kunal Khatua
>             Fix For: 1.11.0
>
>
> See the details in DRILL-5157. The Parquet async reader uses the Snappy library. If the call into Snappy fails (in my case, due to missing dependency management in the Drill pom.xml file), the Parquet reader fails (as it should.)
> Unfortunately, the Parquet reader leaks memory which cause {{IllegalStateException}} errors in production, assertion failures in unit tests.
> To reproduce this the easy way (to avoid the need to undo the fix for DRILL-5157 in Snappy dependencies), use Drill's exception injector in inject an exception at the line where we call into Snappy (See DRILL-5157 for details.)
> Set a breakpoint exception for {{IllegalStateException}} you will see the memory leak. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)