Investigate why cluster aggregate commands that the analyzeShardKey command runs can fail with ShardNotFound

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The jstest added in SERVER-68752 shows that the cluster aggregate command that the analyzeShardKey command on a shardsvr mongod runs can sometimes fail with ShardNotFound error even though there is no failover, shutdown or shard removal. For now, the analyzeShardKey command mitigates this by retrying on a ShardNotFound error. This ticket is to investigate the cause of the error.

            Assignee:
            [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: