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

Rationalize locking behavior for sbe exchange operator

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution

      Currently we take a global lock when on operator open. Is this the right approach?

      Lock::GlobalLock lock(opCtx, MODE_IS);

       

      Without this locking we can fail parallel plans with indexes by asserting here

      boost::optional<KeyStringEntry> seekForKeyString(
      const KeyString::Value& keyStringValue) override {
      dassert(_opCtx>lockState()>isReadLocked());

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            svilen.mihaylov@mongodb.com Svilen Mihaylov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: