[
https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033956#comment-15033956
]
Tsuyoshi Ozawa commented on YARN-4348:
--------------------------------------
[~djp] IMHO, this is a blocker ticket of 2.6.3 and 2.7.3 since the problem is
more serious than I've thought. please check [this
comment|https://issues.apache.org/jira/browse/YARN-4348?focusedCommentId=15018159&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15018159].
This is a unexpected behaviour when RM fails over and it prevents RM fail over
correctly.
> ZKRMStateStore.syncInternal should wait for zkResyncWaitTime instead of
> zkSessionTimeout
> ----------------------------------------------------------------------------------------
>
> Key: YARN-4348
> URL: https://issues.apache.org/jira/browse/YARN-4348
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.2, 2.6.2
> Reporter: Tsuyoshi Ozawa
> Assignee: Tsuyoshi Ozawa
> Priority: Blocker
> Attachments: YARN-4348-branch-2.7.002.patch,
> YARN-4348-branch-2.7.003.patch, YARN-4348-branch-2.7.004.patch,
> YARN-4348.001.patch, YARN-4348.001.patch, log.txt
>
>
> Jian mentioned that the current internal ZK configuration of ZKRMStateStore
> can cause a following situation:
> 1. syncInternal timeouts,
> 2. but sync succeeded later on.
> We should use zkResyncWaitTime as the timeout value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
