[
https://issues.apache.org/jira/browse/HADOOP-16541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shen Yinjie updated HADOOP-16541:
---------------------------------
Summary: RM start fail due to zkCuratorManager connectionTimeoutMs (was:
Make zkCuratorManager connectionTimeoutMs configurabale)
> RM start fail due to zkCuratorManager connectionTimeoutMs
> ----------------------------------------------------------
>
> Key: HADOOP-16541
> URL: https://issues.apache.org/jira/browse/HADOOP-16541
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.1.0
> Reporter: Shen Yinjie
> Assignee: Shen Yinjie
> Priority: Major
>
> Namenode and resourcemanager do the leader election via curator. Currently
> curator's session timeout is defined in CommonConfigurationKeys, but
> connection timeout couldn't be changed (just use curator's hard-coded
> timeout ).
> In some scearios, RM start fail due to connection to zk timeout. We propose
> to add a hadoop configuration for curator's zk connection timeout, so that
> we can deal with this situation better.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
