[
https://issues.apache.org/jira/browse/HADOOP-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906993#action_12906993
]
Matthew Byng-Maddick commented on HADOOP-6210:
----------------------------------------------
Other bits within hadoop try that, but that's not always useful - it turns out
that on Linux there are two ways to bind aliases to interfaces. You can either
create an explicit alias interface - ie. one with a :_n_, such as eth0:1, or
you can use the "iproute" bits to do: /sbin/ip addr add ..., which adds that IP
as an alias on that interface - without creating a separate one. In typical
linux style, this is only visible through the iproute interface (normally via
/sbin/ip), and doesn't surface in ifconfig(8).
The reason for needing to specify the IP address comes out in the VIP case -
where you run an HA of some kind (in my case to co-locate the
namenode/tasktracker with the slaves, and have the namenode always appear on
the same IP address), then the entire point here is to stop the source address
being the VIP - but the VIP is an alias on the interface you would normally
communicate on. The whole thing ends up being a bit of a mess, unfortunately,
and of course the whole thing about nic aliases is particularly platform
specific - solaris uses the names of the drivers: hme0, e1000g0, nge0, FreeBSD
similarly: fxp0 - and again on FreeBSD you can have alias IP addresses - I
think solaris tends to prefer that you use the :1 explicit alias interface.
Linux, of course, is described up above - having the best and worst of both
worlds. All fun.
> Bind Hadoop RPC outgoing to a specific nic
> ------------------------------------------
>
> Key: HADOOP-6210
> URL: https://issues.apache.org/jira/browse/HADOOP-6210
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.20.0
> Reporter: Allen Wittenauer
>
> In environments with multiple interfaces on a machine, it would be useful to
> be able to bind outgoing traffic to specific interfaces rather than letting
> the outbound be picked at random. This is especially important for things
> like Solaris IPMP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
