You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2015/12/08 16:53:11 UTC
[jira] [Issue Comment Deleted] (YARN-4348)
ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding
blocking ZK's event thread
[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junping Du updated YARN-4348:
-----------------------------
Comment: was deleted
(was: Sounds good. Thanks!)
> ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread
> ------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.6.3, 2.7.3
>
> 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)