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

Handle ShardingStateRecovery for catalog shard

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding NYC 2023-02-06, Sharding NYC 2023-02-20

      ShardingStateRecovery will perform a majority write on the config server during shard stepup if a chunk migration or movePrimary was in progress on the previous primary to advance configTime. If this runs on a config server acting as a shard, the write will hang. In 7.0 binaries, the vector clock is used to provide the same guarantees as ShardingStateRecovery, so the majority write is unnecessary for a shard config server, since a config server can only act as a shard in FCV 7.0 and higher. Thus we can avoid the hang by skipping the write on a config server.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: