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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2015/07/29 13:45:05 UTC

[jira] [Commented] (MAPREDUCE-5938) Shuffle port in nodemanager is binding to all IPs

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645910#comment-14645910 ] 

Rohith Sharma K S commented on MAPREDUCE-5938:
----------------------------------------------

I think it would be good to go with user use case. One doubt I have is there are some use cases where two networks are bounded for running jobs. If shuflle port bining to specific ip and ip tables are modified for network bounding, jobs will not run. 
Any thoughts on particular use cases level? 

> 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)