You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (Commented) (JIRA)" <ji...@apache.org> on 2011/12/21 00:11:30 UTC
[jira] [Commented] (MAPREDUCE-3391) Connecting to CM is logged as
Connecting to RM
[ https://issues.apache.org/jira/browse/MAPREDUCE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173600#comment-13173600 ]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3391:
----------------------------------------------------
+1. Very trivial patch. Still applies to trunk. Going to push this in.
> Connecting to CM is logged as Connecting to RM
> ----------------------------------------------
>
> Key: MAPREDUCE-3391
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3391
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 0.23.0
> Reporter: Subroto Sanyal
> Assignee: Subroto Sanyal
> Priority: Minor
> Labels: newbie
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3391.patch
>
>
> In class *org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster*
> {code}
> private void connectToCM() {
> String cmIpPortStr = container.getNodeId().getHost() + ":"
> + container.getNodeId().getPort();
> InetSocketAddress cmAddress = NetUtils.createSocketAddr(cmIpPortStr);
> LOG.info("Connecting to ResourceManager at " + cmIpPortStr);
> this.cm = ((ContainerManager) rpc.getProxy(ContainerManager.class, cmAddress, conf));
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira