Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-79601

Log the SessionId of the cursors a range deletion is going to wait on

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 1

      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

            Assignee:
            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            Reporter:
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: