I don't MR is really the right tool for the JOB you are trying to accomplish.
There are 2 was to add tcp client to an existing o2ib system. 1. Add Lnet Routers to meet the performance goals you have. I would start here it is the least invasive way and the much more documented. http://wiki.lustre.org/LNet_Router_Config_Guide#LNet is a good read on the topic. 2. Add new TCP Nids on your Lustre servers and update the Lustre target. You can serve the same namespace over different fabric types there is some tradeoff with some of the internal RPC for locking and whatnot that can increase the time it takes for some actions to the speed it can do on the slowest fabric. This is an experts only activity to update the nids on existing targets but it is a 2nd way to do it. Thanks, Keith From: lustre-discuss [mailto:[email protected]] On Behalf Of Petrillo, Neale A (Contractor) Sent: Wednesday, November 7, 2018 12:52 PM To: [email protected] Cc: Ault, James R (Contractor) <[email protected]> Subject: [lustre-discuss] Lustre Multi-Rail on 2 Network Types Hello! We have some clients which cannot be attached to our OmniPath network but are attached to the Ethernet network. We were looking at using Multi-Rail on our Lustre servers in order to export the file system on both networks. But, we haven't been able to make much progress. Has anyone done anything like this? If so, how? Do we need to implement an LNet router? Thanks!
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
