[
https://issues.apache.org/jira/browse/HIVE-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates updated HIVE-6635:
-----------------------------
Attachment: HIVE-6635.patch
Added a thread to Driver to send heartbeats. This thread only runs during the
main loop in Driver.execute. I added this in a separate thread because
otherwise I would have needed to add threads in every task to see if heartbeats
needed to be sent. This would be very invasive, and also it's not clear it
would be possible to cover all cases as there are actions that may simply take
a long time (like certain metastore operations). The downside is that a query
will keep running even after it's found out it's locks were aborted and only be
terminated at the end.
> Heartbeats are not being sent when DbLockMgr is used and an operation holds
> locks
> ---------------------------------------------------------------------------------
>
> Key: HIVE-6635
> URL: https://issues.apache.org/jira/browse/HIVE-6635
> Project: Hive
> Issue Type: Bug
> Components: Locking
> Affects Versions: 0.13.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Fix For: 0.13.0
>
> Attachments: HIVE-6635.patch
>
>
> The new DbLockManager depends on heartbeats from the client in order to
> determine that a lock has not timed out. The client is not currently sending
> those heartbeats.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
