hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-509) Setting the network interface for TaskTracker connection to task tracker http server
Date Mon, 21 Jul 2014 20:28:39 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer resolved MAPREDUCE-509.
----------------------------------------

    Resolution: Not a Problem

You can't.  Outbound connections on most Unix platforms will use any available interface.


Closing as not a problem.

> Setting the network interface for TaskTracker connection to task tracker http server
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-509
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-509
>             Project: Hadoop Map/Reduce
>          Issue Type: Wish
>         Environment: Linux RHEL 5.2
>            Reporter: Amnon Katz
>            Priority: Minor
>
> I ma running TestDFSIO using different network interfaces.
> For that, I am modifying the IP address in hadoop-default.xml, hadoop-site.xml and slaves
files in the conf directory.
> Unfortunately, I can still observed connection from TaskTracker to task tracker http
server over the default network interface (eth0) when it is configured to use different network
interface.
> Can you tell me what should be done to be sure that all connection used a unique network
interfaces?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message