[LU-16563] LNet: use discovery ni status to set peer ni availability Created: 16/Feb/23 Updated: 25/Apr/23 Resolved: 11/Apr/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Serguei Smirnov | Assignee: | Serguei Smirnov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Multi-Rail, lnet | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Currently when MR peer is being discovered, it replies with the list of its NIs and their status. Even if NI is "down" due to a "fatal" condition like locally detected "link down", it is listed with "UP" status in the reply, so the recipient can find out that the NI is not reachable only by trying to communicate to it and failing. Instead, to avoid unnecessary delay in this scenario, NI status can be tracked such that locally recognized "down" state is available to any discovering peer. |
| Comments |
| Comment by Gerrit Updater [ 16/Feb/23 ] |
|
"Serguei Smirnov <ssmirnov@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50027 |
| Comment by Gerrit Updater [ 02/Mar/23 ] |
|
"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50188 |
| Comment by Gerrit Updater [ 28/Mar/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50027/ |
| Comment by Gerrit Updater [ 11/Apr/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50188/ |
| Comment by Peter Jones [ 11/Apr/23 ] |
|
Landed for 2.16 |