You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2016/12/08 22:33:58 UTC
[jira] [Commented] (HIVE-11965) add heartbeat count for each
lock/transaction
[ https://issues.apache.org/jira/browse/HIVE-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733596#comment-15733596 ]
Eugene Koifman commented on HIVE-11965:
---------------------------------------
maybe a better strategy is to move heartbeat into the Streaming client.
It's simpler from the caller's perspective and avoids the issue.
> add heartbeat count for each lock/transaction
> ---------------------------------------------
>
> Key: HIVE-11965
> URL: https://issues.apache.org/jira/browse/HIVE-11965
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Affects Versions: 0.14.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
>
> We should add a HEARTBEAT_COUNT column to HIVE_LOCKS and TXNS tables so that queries that update LAST_HEARTBEAT also set HEARTBEAT_COUNT=HEARTBEAT_COUNT + 1.
> This should only be set on explicit heartbeat call, not ones resulting from commits, etc.
> This has low overhead but allows us to detect clients that heartbeat more often than is necessary thus creating useless extra load on metastore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)