[
https://issues.apache.org/jira/browse/HADOOP-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251926#comment-13251926
]
Todd Lipcon commented on HADOOP-8198:
-------------------------------------
bq. Are we going to confine yarn/MR services to using only one NIC?
If I recall correctly, the shuffle services use job tokens and not service
tokens as well, right? I think it's OK to confine the RPC interfaces to using
one NIC (for now) as they're generally not throughput-intensive. Adding
multi-NIC support for them would be nice in the future for fault tolerance but
I think it should be a separate task, since as you've brought up, it's much
harder.
> Support multiple network interfaces
> -----------------------------------
>
> Key: HADOOP-8198
> URL: https://issues.apache.org/jira/browse/HADOOP-8198
> Project: Hadoop Common
> Issue Type: New Feature
> Components: io, performance
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: MultipleNifsv1.pdf, MultipleNifsv2.pdf,
> MultipleNifsv3.pdf
>
>
> Hadoop does not currently utilize multiple network interfaces, which is a
> common user request, and important in enterprise environments. This jira
> covers a proposal for enhancements to Hadoop so it better utilizes multiple
> network interfaces. The primary motivation being improved performance,
> performance isolation, resource utilization and fault tolerance. The attached
> design doc covers the high-level use cases, requirements, a proposal for
> trunk/0.23, discussion on related features, and a proposal for Hadoop 1.x
> that covers a subset of the functionality of the trunk/0.23 proposal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
