[
https://issues.apache.org/jira/browse/MAPREDUCE-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220197#comment-13220197
]
Robert Joseph Evans commented on MAPREDUCE-3761:
------------------------------------------------
The issue is that the AM is arbitrary code. It does not have to be something
that we wrote. The only thing that we can do to restrict it is what the OS
allows us to do. If there is a good way for us to make the OS not allow any
incoming connections to the HTTP port of the AM then I am all for that. Sadly
the HTTP port is an ephemeral port and so is the RPC port that needs to be open
to allow connections from other locations.
I would prefer a different column that can show the host that the AM is running
on. It should come from the RM indicating where it was scheduler, because it
is the AM that reports back both the web app URL and the RPC url.
> AM info in job -list does not reflect the actual AM hostname
> ------------------------------------------------------------
>
> Key: MAPREDUCE-3761
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3761
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Ramya Sunil
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3761-20120202.txt,
> MAPREDUCE-3761-20120214.1.txt
>
>
> The AM info field on "bin/mapred job -list" currently has a value
> <resourcemanager hostname>:8088/proxy/appID. This info is irrelevant unless
> it shows the real information of where the AM was launched. This needs to be
> fixed to show the AM host details.
--
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
