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

SetShardVersion must not call forceShardFilteringMetadataRefresh

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-06-29
    • Linked BF Score:
      26

      Description

      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).

        Attachments

          Activity

            People

            Assignee:
            pierlauro.sciarelli Pierlauro Sciarelli
            Reporter:
            marcos.grillo Marcos José Grillo Ramirez
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: