[
https://issues.apache.org/jira/browse/HIVE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793133#comment-13793133
]
Jason Dere commented on HIVE-5474:
----------------------------------
I don't think a set helps with the de-duping effort, if there is a shared lock
request and exclusive lock request we want to make sure that the exclusive lock
is the one that is kept. So either way we need extra logic to take care of that.
> drop table hangs when concurrency=true
> --------------------------------------
>
> Key: HIVE-5474
> URL: https://issues.apache.org/jira/browse/HIVE-5474
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Locking
> Reporter: Thejas M Nair
> Assignee: Jason Dere
> Attachments: HIVE-5474.1.patch, HIVE-5474.2.patch
>
>
> This is seen in hive 0.12 branch sequential test run.
> TestThriftHttpCLIService.testExecuteStatement
> https://builds.apache.org/job/Hive-branch-0.12-hadoop1/13/testReport/org.apache.hive.service.cli.thrift/TestThriftHttpCLIService/testExecuteStatement/
> stderr has "FAILED: Error in acquiring locks: Locks on the underlying
> objects cannot be acquired. retry after some time"
--
This message was sent by Atlassian JIRA
(v6.1#6144)
