[ https://issues.apache.org/jira/browse/MAPREDUCE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367035#comment-15367035 ]
Naganarasimha G R edited comment on MAPREDUCE-5938 at 7/8/16 1:06 AM: ---------------------------------------------------------------------- Yes, similar to *mapreduce.shuffle.port* we can have this as an mapred-site.xml configuration in each of the NM's mapred-site.xml, they can modify to a specific value. Note sure whether we can support *"0.0.0.0:$\{mapreduce.task.profile.params\}"* as default value instead of deprecating *mapreduce.shuffle.port*. If it can be configured in this way then it would have better compatability was (Author: naganarasimha): Yes, similar to *mapreduce.shuffle.port* we can have this as an mapred-site.xml configuration in each of the NM's mapred-site.xml, they can modify to a specific value. Note sure whether we can support *"0.0.0.0:${mapreduce.task.profile.params}"* as default value instead of deprecating *mapreduce.shuffle.port*. If it can be configured in this way then it would have better compatability > Shuffle port in nodemanager is binding to all IPs > -------------------------------------------------- > > Key: MAPREDUCE-5938 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5938 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Ashutosh Jindal > Assignee: Naganarasimha G R > Attachments: issue.jpg, mapreduce-5938.patch, result_after_fix.jpg > > > nodemanager port mapreduce.shuffle.port is listening to all ip -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org