[LU-16290] Long LNet ping unlink times Created: 02/Nov/22 Updated: 29/Jul/23 Resolved: 14/Nov/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Chris Horn | Assignee: | Chris Horn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
If an lnet ping fails to send an LNET_EVENT_SEND is generated with a non-zero status. However, the ping event handler only calls signals the waiting thread when the unlink event occurs. This means that the thread which issued the ping must wait for full timeout to hit before it wakes up and calls LNetMDUnlink(). The ping event handler should signal completion if we get a non-zero RC on the send event. |
| Comments |
| Comment by Gerrit Updater [ 02/Nov/22 ] |
|
"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49020 |
| Comment by Gerrit Updater [ 14/Nov/22 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49020/ |
| Comment by Peter Jones [ 14/Nov/22 ] |
|
Landed for 2.16 |