hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vihang Karajgaonkar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16213) ObjectStore can leak Queries when rollbackTransaction throws an exception
Date Fri, 28 Apr 2017 17:34:04 GMT

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

Vihang Karajgaonkar commented on HIVE-16213:
--------------------------------------------

org.apache.hadoop.hive.cli.TestAccumuloCliDriver.testCliDriver[accumulo_index] (batchId=225)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=143)

are known flaky tests

I think are related to some PigServer setup issues during the run. I ran them locally and
they were successful. Submitted them again to confirm.

org.apache.hive.hcatalog.pig.TestRCFileHCatStorer.testWriteDate (batchId=178)
org.apache.hive.hcatalog.pig.TestRCFileHCatStorer.testWriteVarchar (batchId=178)
org.apache.hive.hcatalog.pig.TestTextFileHCatStorer.testStoreFuncAllSimpleTypes (batchId=178)


> ObjectStore can leak Queries when rollbackTransaction throws an exception
> -------------------------------------------------------------------------
>
>                 Key: HIVE-16213
>                 URL: https://issues.apache.org/jira/browse/HIVE-16213
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: Alexander Kolbasov
>            Assignee: Vihang Karajgaonkar
>         Attachments: HIVE-16213.01.patch, HIVE-16213.02.patch, HIVE-16213.03.patch, HIVE-16213.04.patch,
HIVE-16213.05.patch, HIVE-16213.06.patch, HIVE-16213.07.patch
>
>
> In ObjectStore.java there are a few places with the code similar to:
> {code}
>     Query query = null;
>     try {
>       openTransaction();
>       query = pm.newQuery(Something.class);
>       ...
>       commited = commitTransaction();
>     } finally {
>       if (!commited) {
>         rollbackTransaction();
>       }
>       if (query != null) {
>         query.closeAll();
>       }
>     }
> {code}
> The problem is that rollbackTransaction() may throw an exception in which case query.closeAll()
wouldn't be executed. 
> The fix would be to wrap rollbackTransaction in its own try-catch block.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message