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

SERVER-78187 Make killing a child session interrupt all sessions associated with it unless the kill is performed by reaping of internal transactions for old retryable writes

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc7
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • v7.0, v6.0
    • Sharding NYC 2023-06-26, Sharding NYC 2023-07-10
    • 106

      Currently, killing a child session doesn't interrupt its parent session or other child sessions. This behavior was introduced in SERVER-66777 to prevent the reaping expired child sessions to interrupt active (parent or child) sessions. However, this has led to deadlock in BF-28922 where a session should have been interrupted by stepdown and wasn't because of this logic. Given that reaping expired child sessions is the only case (that we know of) where killing a child session shouldn't interrupt its parent session or other child sessions, we should make killing a child session interrupt all sessions associated with it in all other cases.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: