You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Wei Zheng (JIRA)" <ji...@apache.org> on 2015/11/02 20:41:27 UTC
[jira] [Commented] (HIVE-12266) When client exists abnormally, it
doesn't release ACID locks
[ https://issues.apache.org/jira/browse/HIVE-12266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985883#comment-14985883 ]
Wei Zheng commented on HIVE-12266:
----------------------------------
Test failures irrelevant. [~ekoifman] Can you take another look?
> When client exists abnormally, it doesn't release ACID locks
> ------------------------------------------------------------
>
> Key: HIVE-12266
> URL: https://issues.apache.org/jira/browse/HIVE-12266
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 1.0.0
> Reporter: Eugene Koifman
> Assignee: Wei Zheng
> Attachments: HIVE-12266.1.patch, HIVE-12266.2.patch, HIVE-12266.3.patch
>
>
> if you start Hive CLI (locking enabled) and run some command that acquires locks and ^C the shell before command completes the locks for the command remain until they timeout.
> I believe Beeline has the same issue.
> Need to add proper hooks to release locks when command dies. (As much as possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)