hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Byng-Maddick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6210) Bind Hadoop RPC outgoing to a specific nic
Date Tue, 07 Sep 2010 23:09:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907020#action_12907020
] 

Matthew Byng-Maddick commented on HADOOP-6210:
----------------------------------------------

When you say "real functional aliases" what do you mean - do you mean _foon_:_m_? If so, then
that doesn't really work on, say, FreeBSD, where the correct way IS to bind addresses using
ifconfig and the "alias" modifier - it doesn't have a concept of _foon_:_m_ - there's a _foon_
interface with a list of inet addresses bound and a list of inet6 addresses and their corresponding
forwarder entries. Linux's 2 methods are both equally supported by the kernel, but less so
by the operating system. It doesn't make one more or less right than the other, and actually,
though it pains me to admit it, using iproute programmatically is significantly neater than
searching to find a free binding on a host with many interface aliases.

As I say, if you want to have, for example, a v6-link-local scoped address - you probably
want to bind by scope (which is almost the same as binding by NIC but not quite).

In v6 I suspect that this kind of problem will get worse, as it's reasonable to have link-local
or site-local addresses bound along with real routeable addresses to interfaces. Even when
dealing with v4  hadoop seems to generally choose the v4-in-v6 space (::ffff:xxx.xxx.xxx.xxx)
for its bindings (so AF_INET6 rather than AF_INET) - on my linux installation, anyway.

What I'm saying, really, is that you kind of need both, but probably prefer IP addresses.

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


Mime
View raw message