hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3492) AM fails to come up because RM and NM can't connect to each other
Date Mon, 20 Apr 2015 18:10:02 GMT

     [ 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)

Mime
View raw message