Missing shard metadata refresh from the CS in coll_timestamp_test.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2021-02-08
    • 12
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The underlying issue is that the test is assuming that after the refineShardKey command the persistent cached metadata on the shards is updated. However, the test is not forcing a refresh so those changes are not visible.

      In order to fix that we could add an explicit refresh of the collection before checking that  the timestamp in config.cache.collections (shard) is the same as in config.collections (config server).

            Assignee:
            Sergi Mateo Bellido
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: