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

Have a better way to enforce internal threads that acquire strong locks are killed during step up/down

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      Currently, internal operations rely on callingĀ setSystemOperationKillable() to allow themselves to be killed by the RstlKillOpThread on step up/down. This design is error-prone and has resulted in bugs like SERVER-40594 and SERVER-43174.

      Instead, we should somehow make the RstlKillOpThread more intelligent on what operations to kill without relying on clients setting the flag. I think we should always kill operations that have intention to acquire strong locks (Mode X/S) because they could be blocked on prepared transactions while holding onto RSTL, preventing step up/down from proceeding.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              lingzhi.deng@mongodb.com Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: