Details
-
Technical task
-
Resolution: Fixed
-
Minor
-
Lustre 2.14.0, Lustre 2.12.4, Lustre 2.15.0
-
9223372036854775807
Description
TCP bonding in socklnd over-complicates the code and there is no evidence it's being used anywhere. With LNet Multi-Rail, the use_tcp_bonding option has become obsolete. Add a deprecation message for earlier releases. Remove it in the 2.15 release.
Multi-Rail feature doesn't need to be explicitly enabled. To use MR instead of the use_tcp_bonding configuration option, group the interfaces on the same network using the lnetctl utility:
lnetctl net add --net tcp --if eth0,eth1
or via the /etc/modprobe.d/lnet.conf or /etc/modprobe.d/lustre.conf configuration file:
options lnet networks="tcp(eth0,eth1)"
and make sure dynamic discovery is enabled:
lnetctl set discovery 1
MR will aggregate the throughput of all available networks/interfaces shared between peer nodes.
See LNet Software Multi-Rail Configuration in the Lustre Operations Manual for more details.
Attachments
Activity
| Fix Version/s | New: Lustre 2.16.0 [ 15190 ] |
| Fix Version/s | Original: Lustre 2.16.0 [ 15190 ] |
| Fix Version/s | New: Lustre 2.16.0 [ 15190 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Link | New: This issue is related to JFC-26 [ JFC-26 ] |
| Link | Original: This issue is related to JFC-23 [ JFC-23 ] |
| Link | New: This issue is related to JFC-23 [ JFC-23 ] |
| Fix Version/s | New: Lustre 2.15.0 [ 14791 ] | |
| Fix Version/s | Original: Lustre 2.14.0 [ 14490 ] | |
| Fix Version/s | Original: Lustre 2.12.7 [ 14793 ] |
| Description |
Original:
TCP bonding in {{socklnd}} over-complicates the code and there is no evidence it's being used anywhere. With LNet Multi-Rail, the {{use_tcp_bonding}} option has become obsolete. Add a deprecation message for earlier releases. Remove it in the 2.15 release.
Multi-Rail feature doesn't need to be explicitly enabled. To use MR instead of the {{use_tcp_bonding}} configuration option, group the interfaces on the same network using the {{lnetctl}} utility: {code:java} lnetctl net add --net tcp --if eth0,eth1 {code} or via the {{/etc/modprobe.d/lnet.conf}} or {{/etc/modprobe.d/lustre.conf}} configuration file: {code:java} options lnet networks="tcp(eth0,eth1)" {code} and make sure dynamic discovery is enabled: {code:java} lnetctl set discovery 1 {code} MR will aggregate the throughput of all available networks/interfaces shared between peer nodes. |
New:
TCP bonding in {{socklnd}} over-complicates the code and there is no evidence it's being used anywhere. With LNet Multi-Rail, the {{use_tcp_bonding}} option has become obsolete. Add a deprecation message for earlier releases. Remove it in the 2.15 release.
Multi-Rail feature doesn't need to be explicitly enabled. To use MR instead of the {{use_tcp_bonding}} configuration option, group the interfaces on the same network using the {{lnetctl}} utility: {code:java} lnetctl net add --net tcp --if eth0,eth1 {code} or via the {{/etc/modprobe.d/lnet.conf}} or {{/etc/modprobe.d/lustre.conf}} configuration file: {code:java} options lnet networks="tcp(eth0,eth1)" {code} and make sure dynamic discovery is enabled: {code:java} lnetctl set discovery 1 {code} MR will aggregate the throughput of all available networks/interfaces shared between peer nodes. See [LNet Software Multi-Rail Configuration|https://doc.lustre.org/lustre_manual.xhtml#lnetmr] in the [Lustre Operations Manual|https://doc.lustre.org/lustre_manual.xhtml] for more details. |
| Fix Version/s | New: Lustre 2.14.0 [ 14490 ] | |
| Fix Version/s | New: Lustre 2.12.7 [ 14793 ] |