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

Ensure having the latest known entry of the catalog cache when creating config.system.sessions

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 5.0.6
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13
    • 35

      After creating and sharding the config.system.sessions collection, there is a refresh that might not notice the creation of the sharded collection.

      This happens because the catalog cache cannot be trusted in secondaries in the config server, specifically, if a config server secondary haven't replicated the write changes and tries to create the indexes then it will end up targeting the config server instead of the shards. We should ensure that the changes have been replicated, we could for example do a write after creating the collection and wait for that configOpTime, or, find a way to get the configOpTime gossiped by the create collection response.

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            0 Vote for this issue
            5 Start watching this issue