[
https://issues.apache.org/jira/browse/MAPREDUCE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061324#comment-13061324
]
Robert Joseph Evans commented on MAPREDUCE-2652:
------------------------------------------------
- When AM launches a container, NM will return a binary blob per service keyed
by service-id. For MR shuffle case, it will return the shuffle service's port.
- AM will get the address for the needed service-id and stores it in the
TaskAttemptImpl so as to use it when it
creates the MapTaskCompletionEvents for the reduces (in TaskImpl).
- I still need to investigate persisting to the task log a bit to know for
sure how to handle this.
> MR-279: Cannot run multiple NMs on a single node
> -------------------------------------------------
>
> Key: MAPREDUCE-2652
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2652
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> Currently in MR-279 the Auxiliary services, like ShuffleHandler, have no way
> to communicate information back to the applications. Because of this the Map
> Reduce Application Master has hardcoded in a port of 8080 for shuffle. This
> prevents the configuration "mapreduce.shuffle.port" form ever being set to
> anything but 8080. The code should be updated to allow this information to
> be returned to the application master. Also the data needs to be persisted
> to the task log so that on restart the data is not lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
