You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/06/01 19:47:19 UTC
[jira] [Resolved] (YARN-3492) AM fails to come up because RM and NM
can't connect to each other
[ https://issues.apache.org/jira/browse/YARN-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved YARN-3492.
-------------------------------------------
Resolution: Cannot Reproduce
Closing this based on previous comments. Please reopen this in case you run into it again.
> 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)