[Lustre-discuss] Could "Client & MGS" or "Client & OSS" running at one node together?
zf5984599 at gmail.com
Wed Mar 7 18:27:12 PST 2012
Dear all, thanks a lot for your answers ;)
Now I have another problem about the network between nodes.
Since there is no Infiniband or 10G-NIC, but I still want to
increase the bandwidth by add more 1G-NICs, I plan to use Linux bonding.
Then, bonding 4 NICs together at one node, BUT there is NO performance
enhanced no matter which bongding mode, described in kernel doc, used.
In stead, the performance of 4-NICs-bonding is lower than 1 NIC's.
Then we use 2 NICs bonding, the performance is better than 1 NIC's.
The result is :
bonding 2 NIC: 1 + 1 > 1
bonding 4 NIC: 1 + 1 + 1 + 1 < 1
The benchmark we used is "netperf".
And I use "tcpdump" to dump the packages, found that there are great
of TCP segments out of orders.
My question is that:
a) TCP segments are out of order, which induced that 4-NIC-bonding
performance decay, is this the root cause?
b) We are doubting the feasibility of this method: using 4-NIC-bonding
to increase bandwidth. Any proposals about that? If so, maybe I should
use some other method instead of this.
Thanks again, all
From: Peter Grandi
Date: 2012-03-07 20:54
To: Lustre discussion
Subject: Re: [Lustre-discuss] Could "Client & MGS" or "Client & OSS" running at one node together?
> Since there is no more node in our project when using Lustre,
> I want to confirm that:
> 1) Could the "Client" and "MGS" run at one node together? or
> could "Client" and "OSS" run at one node together? 2) Suppose
> I had deployed them at one node, what potential shortcomings
> or harm are there?
Running MGS and MDS on the same nodes is customary, see:
Running the MGS, MDS and OSS service on the same node is
possible and fairly common in very small setups, usually those
in which there is only 1-2 nodes.
It is possible to use the client code on all types of Lustre
servers, but at least in the case of using the client code on an
OSS there is the non-negligible possibility of a resource
deadlock, if the client uses the OSS on the same node, as the
client and OSS codes compete for memory, so in the past this has
This is documented here:
«Caution - Do not do this when the client and OSS are on the
same node, as memory pressure between the client and OSS can
lead to deadlocks.»
Lustre-discuss mailing list
Lustre-discuss at lists.lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lustre-discuss