[
https://issues.apache.org/jira/browse/HIVE-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218356#comment-14218356
]
Sushanth Sowmyan commented on HIVE-8850:
----------------------------------------
Yeah, I agree HIVE-8891 is different, and is necessary as well - I called you
guys in here so that I have more people familiar with this looking at this as
well. :)
And yes, the patch provided here would still not solve the issue. It's a good
first step in that it solves the issue of commitTransaction after a
rollbackTransaction where the connection is invalidated in the background by
something else, such as bonecp, but it does not yet solve the issue of an
openTransaction after a rollbackTransaction in a nested scope.
> ObjectStore:: rollbackTransaction() should set the transaction status to
> TXN_STATUS.ROLLBACK irrespective of whether it is active or not
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-8850
> URL: https://issues.apache.org/jira/browse/HIVE-8850
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-8850.1.patch
>
>
> We can run into issues as described below:
> Hive script adds 2800 partitions to a table and during this it can get a
> SQLState 08S01 [Communication Link Error] and bonecp kill all the connections
> in the pool. The partitions are added and a create table statement executes
> (Metering_IngestedData_Compressed). The map job finishes successfully and
> while moving the table to the hive warehouse the ObjectStore.java
> commitTransaction() raises the error: commitTransaction was called but
> openTransactionCalls = 0. This probably indicates that there are unbalanced
> calls to openTransaction/commitTransaction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
