Align LNet routing with Multi-Rail and LNet health
(LU-11297)
|
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.13.0 |
| Type: | Technical task | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Amir Shehata (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | lnet-health | ||
| Issue Links: |
|
||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
In case of routers (as well as for the general case) it's important to update the health of the ni/lpni for incoming messages. For an lpni specifically when we receive a message is when we know that the lpni is up. A percentage router health is required in order to send a message to a gateway. That defaults to 100, meaning that a router interface has to be absolutely healthy in order to send to it. This matches the current behavior. So if a router interface goes down an its health goes down significantly, but then it comes back up again; either we receive a message from it or we discover it and get a reply, then in order to start using that router interface again we have to boost its health all the way up to maximum. This behavior is special cased for routers. |
| Comments |
| Comment by Gerrit Updater [ 05/Oct/18 ] |
|
Amir Shehata (ashehata@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/33301 |
| Comment by Gerrit Updater [ 07/Jun/19 ] |
|
Amir Shehata (ashehata@whamcloud.com) merged in patch https://review.whamcloud.com/33301/ |
| Comment by Joseph Gmitter (Inactive) [ 10/Jun/19 ] |
|
Work has landed as part of the MR Routing merge commit: https://review.whamcloud.com/#/c/34983/ |
| Comment by Gerrit Updater [ 24/Apr/20 ] |
|
Olaf Faaland-LLNL (faaland1@llnl.gov) uploaded a new patch: https://review.whamcloud.com/38354 |
| Comment by Gerrit Updater [ 24/Apr/20 ] |
|
Olaf Faaland-LLNL (faaland1@llnl.gov) uploaded a new patch: https://review.whamcloud.com/38357 |
[LU-11477]