[
https://issues.apache.org/jira/browse/HADOOP-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HADOOP-15449:
----------------------------------------
Description:
We observed from several users regarding Namenode flip-over is due to either
zookeeper disk slowness (higher fsync cost) or network issue. We would need to
avoid flip-over issue to some extent by increasing HA session timeout,
ha.zookeeper.session-timeout.ms.
Default value is 5000 ms, seems very low in any production environment. I
would suggest 10000 ms as default session timeout.
was:
We observed from several users regarding Namenode flip-over is due to either
zookeeper disk slowness (higher fsync cost) or network issue. We would need to
avoid flip-over issue to some extent by increasing HA session timeout,
ha.zookeeper.session-timeout.ms.
Default value 5000 ms, seems very low in any production environment. I would
suggest 10000 ms as default session timeout.
> Frequent Namenode Flipover affecting user Jobs.
> -----------------------------------------------
>
> Key: HADOOP-15449
> URL: https://issues.apache.org/jira/browse/HADOOP-15449
> Project: Hadoop Common
> Issue Type: Wish
> Components: common
> Affects Versions: 2.7.4
> Reporter: Karthik Palanisamy
> Priority: Critical
> Attachments: HADOOP-15449.patch
>
>
> We observed from several users regarding Namenode flip-over is due to either
> zookeeper disk slowness (higher fsync cost) or network issue. We would need
> to avoid flip-over issue to some extent by increasing HA session timeout,
> ha.zookeeper.session-timeout.ms.
> Default value is 5000 ms, seems very low in any production environment. I
> would suggest 10000 ms as default session timeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
