[LU-14057] Quiet innacurate log message on server side Created: 21/Oct/20 Updated: 28/Jan/22 Resolved: 03/Nov/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0, Lustre 2.12.5 |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Aurelien Degremont (Inactive) | Assignee: | Aurelien Degremont (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
When a client connects to a target, this establishes a client -> server export connection and a corresponding reverse import connection, from target to client. This reverse import connection adds a "Connection restored at ... " log message even if this is the first connection. Reverse imports maintain a target -> client connection which does not support recovery as client don't run a recovery. At every connection, the reverse import state goes from NEW to RECOVER to FULL which triggers a Connection restored log message, even if this is the first connection from this client. I think we can simply suppress this log message for reverse import to avoid this noise. |
| Comments |
| Comment by Gerrit Updater [ 21/Oct/20 ] |
|
Aurelien Degremont (degremoa@amazon.com) uploaded a new patch: https://review.whamcloud.com/40331 |
| Comment by Gerrit Updater [ 03/Nov/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/40331/ |
| Comment by Peter Jones [ 03/Nov/20 ] |
|
Landed for 2.14 |