Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Wed, 30 Apr 2014 04:03:24 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12711376.1398830576057.204504.1398830604736@arcas>
In-Reply-To: <JIRA.12711376.1398830576057@arcas>
References: <JIRA.12711376.1398830576057@arcas>
Subject: [jira] [Created] (YARN-2000) Fix ordering of starting services
 inside the RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Jian He created YARN-2000:
-----------------------------

             Summary: Fix ordering of starting services inside the RM
                 Key: YARN-2000
                 URL: https://issues.apache.org/jira/browse/YARN-2000
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Jian He
            Assignee: Jian He


The order of starting services in RM would be:
- Recovery of the app/attempts
- Start the scheduler and add scheduler app/attempts
- Start ResourceTrackerService and re-populate the containers in scheduler =
based on the containers info from NMs=20
- ApplicationMasterService either don=E2=80=99t start or start but block un=
til all the previous NMs registers.

Other than these, there are other services like ClientRMService, Webapps wh=
ich we need to  think about the order too.


--
This message was sent by Atlassian JIRA
(v6.2#6252)