[
https://issues.apache.org/jira/browse/MAPREDUCE-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261309#comment-14261309
]
Avner BenHanoch commented on MAPREDUCE-4168:
--------------------------------------------
{quote}
If one only needs to listen on one interface, then only that interface should
be configured in the *-site.xml files.
{quote}
Thanks for the correction. you can replace slaves file with *-site.xml files
in my previous comment.
{quote}
using a custom set of *-site.xml files installed on client nodes to specify
that the RM is actually at 10.1.2.3 (or whatever) is a viable workaround. But
it effectively tosses the problem over the wall...
{quote}
FWIW, In hadoop-1 I used
{code}
<property> <name>slave.host.name </name> <value>${MYDESIREDIP}</value>
</property>
{code}
and added to hadoop-env.sh something like:
{code}
export HADOOP_OPTS="-DMYDESIREDIP=`hostanme`.domain.of.my.secondary.interface
${HADOOP_OPTS}"
{code}
(notice the back tick around `hostanme`. This was resolved uniquely to my
specific secondary interface on each machine). Unfortunately, this trick
doesn't work in yarn. Perhaps it is simple to restore it.
> Support multiple network interfaces
> -----------------------------------
>
> Key: MAPREDUCE-4168
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4168
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Tom White
>
> Umbrella jira to track the MapReduce side of HADOOP-8198.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
