Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Sat, 24 Dec 2016 00:59:58 +0000 (UTC)
From: "Paul Rogers (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.13030453.1482541143000.591794.1482541198518@Atlassian.JIRA>
In-Reply-To: <JIRA.13030453.1482541143000@Atlassian.JIRA>
References: <JIRA.13030453.1482541143000@Atlassian.JIRA> <JIRA.13030453.1482541143498@arcas>
Subject: [jira] [Created] (DRILL-5160) Memory leak in Parquet async reader
 when Snappy fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Dec 2016 01:00:00 -0000

Paul Rogers created DRILL-5160:
----------------------------------

             Summary: 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: Parth Chandra


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.3.4#6332)