Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 30 Sep 2015 18:15:04 +0000 (UTC)
From: "Anubhav Dhoot (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12888625.1442599191000.121566.1443636904675@Atlassian.JIRA>
In-Reply-To: <JIRA.12888625.1442599191000@Atlassian.JIRA>
References: <JIRA.12888625.1442599191000@Atlassian.JIRA>
 <JIRA.12888625.1442599191181@arcas>
Subject: [jira] [Updated] (YARN-4185) Retry interval delay for NM client can
 be improved from the fixed static retry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anubhav Dhoot updated YARN-4185:
--------------------------------
    Assignee: Neelesh Srinivas Salian  (was: Anubhav Dhoot)

> Retry interval delay for NM client can be improved from the fixed static retry 
> -------------------------------------------------------------------------------
>
>                 Key: YARN-4185
>                 URL: https://issues.apache.org/jira/browse/YARN-4185
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Anubhav Dhoot
>            Assignee: Neelesh Srinivas Salian
>
> Instead of having a fixed retry interval that starts off very high and stays there, we are better off using an exponential backoff that has the same fixed max limit. Today the retry interval is fixed at 10 sec that can be unnecessarily high especially when NMs could rolling restart within a sec.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)