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

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: