[SERVER-79601] Log the SessionId of the cursors a range deletion is going to wait on Created: 02/Aug/23  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Silvia Surroca Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-71792 Log list of cursors a range deletion ... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 1

 Description   

Currently, we are dumping a list with the cursor ids a range deletion is going to wait on into the logs, which is a valuable information in case the range-deleter is slow or gets stuck.

However, it's not easy to find the operation that belongs to a specific CursorId, so it's still hard to debug scenarios where range-deleter gets stuck.

The purpose of this ticket is to add more information about the cursors instead of just the CursorId.

This is the proposed list of attributes to fetch from the CursorManager here and add to this log statement:

  • SessionId
  • TxnNumber
  • OriginatingCommand
  • NBatches

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