[LU-13472] lnet: routing aliveness might be stale Created: 22/Apr/20 Updated: 27/May/20 Resolved: 27/May/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Amir Shehata (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
In the case when the discover is toggled from on to off, the route aliveness might become stale due to not updating the route->lr_alive variable correctly. It will get updated once the gateway is pinged, however, there is a period of max alive_router_check_interval where the route can be down. |
| Comments |
| Comment by Gerrit Updater [ 23/Apr/20 ] |
|
Amir Shehata (ashehata@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/38323 |
| Comment by Gerrit Updater [ 27/May/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38323/ |
| Comment by Peter Jones [ 27/May/20 ] |
|
Landed for 2.14 |