You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Omkar Vinit Joshi (JIRA)" <ji...@apache.org> on 2013/11/22 03:12:36 UTC
[jira] [Created] (YARN-1436) ZKRMStateStore should have separate
configuration for retry period.
Omkar Vinit Joshi created YARN-1436:
---------------------------------------
Summary: ZKRMStateStore should have separate configuration for retry period.
Key: YARN-1436
URL: https://issues.apache.org/jira/browse/YARN-1436
Project: Hadoop YARN
Issue Type: Bug
Reporter: Omkar Vinit Joshi
Assignee: Jian He
Problem :- Today we have zkSessionTimeout period which is getting used for zookeeper session timeout and for ZKRMStateStore based retry policy.
Proposed suggestion :- Ideally we should have different configuration knobs for this.
Ideal values for
zkSessionTimeout should be :- number of zookeeper instances participating in quorum * per zookeeper session timeout. see
{code}
org.apache.zookeeper.ClientCnxn.ClientCnxn()..
connectTimeout = sessionTimeout / hostProvider.size();
{code}
retry policy... (may be retry time period or count)
--
This message was sent by Atlassian JIRA
(v6.1#6144)