[
https://issues.apache.org/jira/browse/HIVE-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772313#comment-13772313
]
Jonathan Sharley commented on HIVE-4996:
----------------------------------------
We have seen similar issues in an environment with a lot of concurrent hive
access from multiple machines all running version 0.11. Our first thought was
that we needed to turn on hive.support.concurrency. However, after doing this
on all of our hosts including the ones running hiveserver we still see an
intermittent issue. I've not been able to reliably reproduce it, but it does
happen at least a few times a day as part of our regularly scheduled jobs.
> unbalanced calls to openTransaction/commitTransaction
> -----------------------------------------------------
>
> Key: HIVE-4996
> URL: https://issues.apache.org/jira/browse/HIVE-4996
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.10.0
> Environment: hiveserver1 Java HotSpot(TM) 64-Bit Server VM (build
> 20.6-b01, mixed mode)
> Reporter: wangfeng
> Priority: Critical
> Labels: hive, metastore
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> when we used hiveserver1 based on hive-0.10.0, we found the Exception
> thrown.It was:
> FAILED: Error in metadata: MetaException(message:java.lang.RuntimeException:
> commitTransaction was called but openTransactionCalls = 0. This probably
> indicates that the
> re are unbalanced calls to openTransaction/commitTransaction)
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask
> help
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
