Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 20 Apr 2015 18:10:02 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12821288.1429129533000.50052.1429553402716@Atlassian.JIRA>
In-Reply-To: <JIRA.12821288.1429129533000@Atlassian.JIRA>
References: <JIRA.12821288.1429129533000@Atlassian.JIRA>
 <JIRA.12821288.1429129533484@arcas>
Subject: [jira] [Updated] (YARN-3492) AM fails to come up because RM and NM
 can't connect to each other
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated YARN-3492:
------------------------------------------
    Target Version/s: 2.7.1  (was: 2.7.0)

bq. I took your mapred-site.xml and yarn-site.xml and started the pseudo-distributed cluster.. Containers are getting allocated and NM able connect to RM..
I suspect an env issue. Moving this out to 2.7.1. [~kasha]?

> AM fails to come up because RM and NM can't connect to each other
> -----------------------------------------------------------------
>
>                 Key: YARN-3492
>                 URL: https://issues.apache.org/jira/browse/YARN-3492
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>         Environment: pseudo-distributed cluster on a mac
>            Reporter: Karthik Kambatla
>            Priority: Blocker
>         Attachments: mapred-site.xml, yarn-kasha-nodemanager-kasha-mbp.local.log, yarn-kasha-resourcemanager-kasha-mbp.local.log, yarn-site.xml
>
>
> Stood up a pseudo-distributed cluster with 2.7.0 RC0. Submitted a pi job. The container gets allocated, but doesn't get launched. The NM can't talk to the RM. Logs to follow. 


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