SetShardVersion must not call forceShardFilteringMetadataRefresh

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2020-06-29
    • 26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On SERVER-48883 an invariant was added into the migration recovery to detect if any other operation could race while refreshing the shard version.

      The following incorrect behavior has been found: with mongos version 4.4 and shards mongod version master, a stale shard version error triggers a set shard version request on the shard's primary forcing a forceShardFilteringMetadataRefresh.

      A solution can be calling onShardVersionMismatch in order to wait for an eventual recovery/refresh.

      Not happening with mongos master because the version manager has been deleted in SERVER-47426 (commit).

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Marcos José Grillo Ramirez
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: