Fix ReplicationCoordinator::runCmdOnPrimaryAndAwaitResponse header comment

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Comment states cmd will run on a DBDirectClient if the node is primary, or AsyncDBClient otherwise. After SERVER-48235 this is no longer true, and the command always runs with AsyncDBClient.

      https://github.com/10gen/mongo/blob/b62723290a994c445b9f1740c642fce79ffe07bd/src/mongo/db/repl/replication_coordinator.h#L1141

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: