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

Avoid clearing filtering metadata after failed metadata refresh

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 5.0.14
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v5.0
    • Sharding EMEA 2021-11-01

      This clearFilteringMetadata after a failed refresh shouldn't be necessary. In that situation, the exception is already propagated to the caller of onShardVersionMismatch. Moreover, on the following requests that do shardVersion checking, onShardVersion mismatch should already be called anyway if the metadata was unknown/stale; so there should not be a need to explicitly clear the filtering metadata.

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: