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

OperationContext API should have way to request being killed on stepdown even if a global lock has not been taken

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Replication, Sharding
    • None
    • Sharding

    Description

      Right now, sharding has been working around this issue by acquiring and immediately releasing a global IX lock, see example here.

      Assigning to the sharding backlog for now, but it might make sense to be owned by Service Architecture or Replication.

      Attachments

        Issue Links

          duplicates

          Task - A task that needs to be done. SERVER-49237 Add a way for OperationContexts to opt-in to always getting interrupted at stepdown

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

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: