[LU-13478] LNet: peer update adjustment on discovery toggle Created: 23/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 |
|
Do not delete a non-MR peer when it first connects. We should only delete a peer from our local database iff we've already discovered it and it's state is changing from discovery on to discovery off. I think it is better to do a push to the peers only when discovery is toggled from on to off. This lets the peers know to clear their representation of the node. When it attempts to connect to it after, it'll get the correct list of NIDs. However in the reverse case; discovery going from off to on, the PUSH can be sent on an interface which is not recorded on the far side. The push is dropped in this case. By not pushing when we go from off to on we avoid this scenario and allow the peer to rediscover when it commences communication. |
| Comments |
| Comment by Gerrit Updater [ 23/Apr/20 ] |
|
Amir Shehata (ashehata@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/38321 |
| Comment by Gerrit Updater [ 27/May/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38321/ |
| Comment by Peter Jones [ 27/May/20 ] |
|
Landed for 2.14 |