hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12266) When client exists abnormally, it doesn't release ACID locks
Date Sat, 31 Oct 2015 00:26:27 GMT

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

Wei Zheng commented on HIVE-12266:
----------------------------------

Makes sense. But based on my experiments, the transaction manager was there in Driver constructor.
Maybe we get it from the previous query in the same session? Is transaction manager corresponding
to a session or to a query?

> 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
>
>
> 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)

Mime
View raw message