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

Investigate how overrideShardIdentity could differ at Config and shard servers

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

      overrideShardIdentity when starting in read-only queryable backup mode queryableBackupMode mode is opposite between Config and Shard servers. Properly handling this requires to track down the actual usage of shardIdentity document and narrow down its handling to the server “role”.

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: