Hello, Could you file a JIRA for this please? Currently the ShuffleHandler will always bind to wildcard address due to the code being that way (in both branch-2 and trunk presently: https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java#L388 ).
Your current workaround would be to use a firewall to drop out external connections to that port. On Tue, Dec 8, 2015 at 9:30 PM Varun Vasudev <[email protected]> wrote: > Hi Li, > > What have you set yarn.nodemanager.bind-host to? From > https://hadoop.apache.org/docs/r2.7.1/hadoop-yarn/hadoop-yarn-common/yarn-default.xml > - > > "The actual address the server will bind to. If this optional address is > set, the RPC and webapp servers will bind to this address and the > port specified in > yarn.nodemanager.address and yarn.nodemanager.webapp.address, > respectively. This is > most useful for making NM listen to all interfaces by setting to > 0.0.0.0” > > -Varun > > > > On 12/8/15, 2:57 PM, "Li Li" <[email protected]> wrote: > > > I want to setup a yarn cluster. It's not allowed to visit from > >public network so I changed many configuration files to let all > >service bind to the internal network address. > > All thing is fine exception the nodemanager which bind > >0.0.0.0:13562. I searched the default-mapred-default.xml and found it > >mapreduce.shuffle.port. > > Which configuration file should I change to let nodemanager listen > >on internal address instead of 0.0.0.0? > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [email protected] > >For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
