hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4168) Support multiple network interfaces
Date Wed, 31 Dec 2014 10:24:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262085#comment-14262085

Rajiv Chittajallu commented on MAPREDUCE-4168:

Restricting access to nodes managed by YARN by using proxies for outbound access:

Cant this restriction be enforced via firewall, limiting external clients to only reach RM?
Having separate physical network for RM to NM vs RM to clients assumes one can easily protect
RM host instead of using a firewall to restrict access to nodes running nodemanagers. 

Reading through other comments and Hadoop-8198, requirement for multi homed network support
is for redundancy and performance. This can't just be implemented by adding multiple IP's.

Admin/oob vs cluster network:

YARN and HDFS could function with out being aware of admin network.

Non HDFS access:

Changes proposed in this Jira are for core hadoop services. Network requirements for no hdfs
access is up to respective client implementation. Compute node can have a Luster configured
to use OFED infinband. This doesn't require changes to hdfs or yarn. Masters can be bound
to one network. 
YARN could add support to manage interconnect as a resource.



> 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

View raw message