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

Add a log line for when a cursor is reaped due to logical session cleanup

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v4.2, v4.0, v3.6
    • Sharding 2019-10-07, Sharding 2019-10-21, Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16

    Description

      When a cursor is cleaned up because of logical session killing (either logical session timeout, or a killSessions command), it currently cleans up silently. This is non-obvious for users (especially when using no timeout cursors and default sessions).

      It would be a useful diagnostic if that cleanup triggered a log line explaining the reason for the kill

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-45385 Unblacklist sharding/kill_sessions.js after SERVER-43246 backports have reached last-stable

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-45385 Unblacklist sharding/kill_sessions.js after SERVER-43246 backports have reached last-stable

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              kevin.pulo@mongodb.com Kevin Pulo
              jason.carey@mongodb.com Jason Carey
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: