[
https://issues.apache.org/jira/browse/HADOOP-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249963#comment-13249963
]
Sanjay Radia commented on HADOOP-8198:
--------------------------------------
> .. host-level bonding works today as long as the IP of bond is where IPC
> comes from as well ...
Hence if Hadoop is correctly configured then multiple NICs work for use case 1.
Eli, how important is use case 2 for Hadoop users?
One of my concerns is that this code change is going to have some tricky corner
cases to get right based on experience with the recent ipAddress-dnsName change
patch (forget jira number) that resulted in some subtle bugs down the road with
tokens etc.
> 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
