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

Split and Merge commands need to refresh filtering metadata before checking preconditions

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc1, 6.2.0-rc0
    • Affects Version/s: 6.1.0-rc1, 6.2.0-rc0
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.1
    • Sharding EMEA 2022-09-05
    • 35

      As part of SERVER-68485, we stopped sending the shard version in split and merge commands and instead checked the preconditions of the commands outside of the shard versioning protocol (similar to what is done in move chunks). However, if the filtering information is stale, the StaleConfigInfo will contain ShardVersion::IGNORED and the shard will not refresh, even if the shard is actually staler than the router.
      One way to solve this would be to add a call to onShardVersionMismatch before the metadata checks in split and merge, similar to what is done in move chunk.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: