[jira] [Updated] (YARN-4348) ZKRMStateStore.syncInternal should wait for zkResyncWaitTime instead of zkSessionTimeout

["Tsuyoshi Ozawa (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsuyoshi Ozawa updated YARN-4348:
---------------------------------
    Attachment: YARN-4348-branch-2.7.004.patch

Adding missing {{continue}} statement after calling {{syncInternal}} in the following block:

{code}
          if (shouldRetryWithNewConnection(ke.code()) && retry < numRetries) {
            LOG.info("Retrying operation on ZK with new Connection. " +
                "Retry no. " + retry);
            Thread.sleep(zkRetryInterval);
            createConnection();
            syncInternal(ke.getPath());
            continue;
          }
{code}

> 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)