[SERVER-77610] Log session id associated with the backup cursor Created: 30/May/23  Updated: 29/Oct/23  Resolved: 12/Jul/23

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: 6.0.0-rc13, 7.1.0-rc0, 4.4.25, 7.0.2, 5.0.22

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Shin Yee Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.3, v6.0, v5.0, v4.4
Sprint: Execution NAMR Team 2023-07-10, Execution NAMR Team 2023-07-24
Participants:
Case:

 Description   

At present the log message reporting establishement of a backup cursor does not include a session id used by the client.

{"t":{"$date":"2023-05-31T09:46:31.715+10:00"},"s":"I",  "c":"STORAGE",  "id":24200,   "ctx":"conn11","msg":"Opened backup cursor","attr":{"backupId":{"uuid":{"$uuid":"eb00127c-48f6-42ba-a638-f6da12c19e4e"}},"term":-1}}

This makes it hard to diagnose situations when the backup cursor does not get reaped for a long time.

It would be helpful to include a session id in the log message as well.


Generated at Thu Feb 08 06:36:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.