[
https://issues.apache.org/jira/browse/HIVE-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885911#comment-13885911
]
Sergey Shelukhin commented on HIVE-4996:
----------------------------------------
There's attribute in retryingrawstore I think that prevents commit itself from
being retries.
Perhaps it (or something similar?) can also be used to prevent write ops from
being retried? Retrying read ops might make sense.
> 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, 0.11.0, 0.12.0
> Environment: hiveserver1 Java HotSpot(TM) 64-Bit Server VM (build
> 20.6-b01, mixed mode)
> Reporter: wangfeng
> Assignee: Szehon Ho
> Priority: Critical
> Labels: hive, metastore
> Attachments: hive-4996.path
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
