Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 26 Jan 2016 19:36:40 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12908753.1446077248000.215703.1453837000342@Atlassian.JIRA>
In-Reply-To: <JIRA.12908753.1446077248000@Atlassian.JIRA>
References: <JIRA.12908753.1446077248000@Atlassian.JIRA>
 <JIRA.12908753.1446077248929@arcas>
Subject: [jira] [Updated] (YARN-4313) Race condition in MiniMRYarnCluster
 when getting history server address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated YARN-4313:
------------------------------------------
    Fix Version/s:     (was: 2.8.0)

> Race condition in MiniMRYarnCluster when getting history server address
> -----------------------------------------------------------------------
>
>                 Key: YARN-4313
>                 URL: https://issues.apache.org/jira/browse/YARN-4313
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>            Assignee: Jian He
>             Fix For: 2.7.2
>
>         Attachments: YARN-4313.1.patch, YARN-4313.2.patch
>
>
> Problem in this place when waiting for JHS to be started
> {code}
>         new Thread() {
>           public void run() {
>             historyServer.start();
>           };
>         }.start();
>         while (historyServer.getServiceState() == STATE.INITED) {
>           LOG.info("Waiting for HistoryServer to start...");
>           Thread.sleep(1500);
>         }
> {code}
> The service state is updated before the service is actually started. See AbstractServic#start.  So it's possible that when the while loop breaks, the service is not yet started. 


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