[
https://issues.apache.org/jira/browse/HIVE-20854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675722#comment-16675722
]
Peter Vary commented on HIVE-20854:
-----------------------------------
[~gopalv]: You might be interested in the discussion here: HIVE-14979.
[~thejas] wrote at that time:
{quote}
Regarding the session timeout -
Looks like the original setting for the session timeout was 10 mins, and
HIVE-9119 changed it to 20 mins.
In case of zookeeper service discovery, it is not a major issue if the entry in
zookeeper stays around for longer. Larger timeout can provide better resilience
against temporary gc or network issues. 10 mins might be still OK for this
purpose.
{quote}
I am not sure the things mentioned are still valid, but I hope this info could
help.
Thanks,
Peter
> Sensible Defaults: Hive's Zookeeper heartbeat interval is 20 minutes, change
> to 2
> ---------------------------------------------------------------------------------
>
> Key: HIVE-20854
> URL: https://issues.apache.org/jira/browse/HIVE-20854
> Project: Hive
> Issue Type: Bug
> Reporter: Gopal V
> Assignee: Gopal V
> Priority: Major
> Attachments: HIVE-20854.1.patch
>
>
> {code}
> HIVE_ZOOKEEPER_SESSION_TIMEOUT("hive.zookeeper.session.timeout",
> "1200000ms",
> new TimeValidator(TimeUnit.MILLISECONDS),
> "ZooKeeper client's session timeout (in milliseconds). The client is
> disconnected, and as a result, all locks released, \n" +
> "if a heartbeat is not sent in the timeout."),
> {code}
> That's 1,200,000ms which is too long for all practical purposes - a 20 minute
> outage in case a node has a failure is too long.
> That is too long for the JDBC load-balancing, LLAP failure tolerance and the
> lock manager expiry.
> Change to 2 minutes, as a sensible default
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
