Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 5 Feb 2015 01:27:35 +0000 (UTC)
From: "Jun Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12769611.1422010315000.261016.1423099655907@Atlassian.JIRA>
In-Reply-To: <JIRA.12769611.1422010315000@Atlassian.JIRA>
References: <JIRA.12769611.1422010315000@Atlassian.JIRA>
 <JIRA.12769611.1422010315939@arcas>
Subject: [jira] [Updated] (YARN-3094) reset timer for liveness monitors
 after RM recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jun Gong updated YARN-3094:
---------------------------
    Attachment: YARN-3094.5.patch

The failed test case seems unrelated. Re-submit the same patch.

> reset timer for liveness monitors after RM recovery
> ---------------------------------------------------
>
>                 Key: YARN-3094
>                 URL: https://issues.apache.org/jira/browse/YARN-3094
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>         Attachments: YARN-3094.2.patch, YARN-3094.3.patch, YARN-3094.4.patch, YARN-3094.5.patch, YARN-3094.patch
>
>
> When RM restarts, it will recover RMAppAttempts and registry them to AMLivenessMonitor if they are not in final state. AM will time out in RM if the recover process takes long time due to some reasons(e.g. too many apps). 
> In our system, we found the recover process took about 3 mins, and all AM time out.


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