[
https://issues.apache.org/jira/browse/HIVE-14263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389881#comment-15389881
]
Thejas M Nair commented on HIVE-14263:
--------------------------------------
Regarding tryLock. tryLock() doesn't honor the waiting queue, ie it jumps in
middle of the queue. So even if there are 10 other threads blocked on the lock
call, a newer query might get the lock. Giving priority to ones that have been
waiting longer would result in more predictable behavior for user.
Regagrding "lock acquired" message, for queries that don't immediately return
results or print another message, the users (and hadoop admins) are likely to
suspect that it is still stuck at waiting for lock. But it might be stuck
somewhere else (maybe an issue with yarn for example).
Hopefully, the cases where query waits on the compile lock won't be that common.
> Log message when HS2 query is waiting on compile lock
> -----------------------------------------------------
>
> Key: HIVE-14263
> URL: https://issues.apache.org/jira/browse/HIVE-14263
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Thejas M Nair
> Assignee: Tao Li
> Attachments: HIVE-14263.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
