[
https://issues.apache.org/jira/browse/YARN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714291#comment-13714291
]
Omkar Vinit Joshi commented on YARN-944:
----------------------------------------
By default resolve ip is set to true...
{code}
boolean useIp = conf.getBoolean(
CommonConfigurationKeys.HADOOP_SECURITY_TOKEN_SERVICE_USE_IP,
CommonConfigurationKeys.HADOOP_SECURITY_TOKEN_SERVICE_USE_IP_DEFAULT);
setTokenServiceUseIp(useIp);
{code}
can you try setting below parameter?
{code}
<property>
<name>yarn.resourcemanager.scheduler.address</name>
<value>localhost:54313</value> <!-- your resource manager scheduler
address -->
<description>host is the hostname of the resourcemanager and port is the
port
on which the Applications in the cluster talk to the Resource Manager.
</description>
</property>
{code}
I don't know whether we need to fix this..
> App failed with container launch failed even though container started
> ---------------------------------------------------------------------
>
> Key: YARN-944
> URL: https://issues.apache.org/jira/browse/YARN-944
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Bikas Saha
> Assignee: Omkar Vinit Joshi
> Attachments: nm.log, rm.log, yarn-site.xml
>
>
> The container is the AM container. It started and the AM failed during RM
> registration. The error message presented was about container launch failing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
