[
https://issues.apache.org/jira/browse/MAPREDUCE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048095#comment-15048095
]
Harsh J commented on MAPREDUCE-5938:
------------------------------------
Shouldn't the fix follow the usual configurable approach as with other binding
properties in Hadoop? A property X that's set to 0.0.0.0 by default, but can be
set to a hostname/IP if it needs to be limited. Provide the property's value as
an InetAddress (with the port property) to the bind command.
The current patch would cause a limitation of those that already are relying on
the wildcard feature today.
> AM tracking URL & 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)
