Sharded index commands shouldn't target primary shard if it doesn't own chunks

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2019-12-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since SERVER-44720 was implemented, the requirement that the primary shard for a sharded collection always has correct indexes even when it owns no chunks has been dropped, so the logic to always target the primary shard should be removed.

              Assignee:
              Cheahuychou Mao
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: