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

Wait for config.system.sessions collection to exist on the config server before refreshing logical session cache

    • Fully Compatible
    • ALL
    • v5.1, v5.0, v4.4
    • Sharding 2021-11-01
    • 21

      In verify_sessions_expiration_sharded.js, we refresh the logical session cache on mongos before guaranteeing that every config server node has replicated the chunk metadata associated with the sessions collection. We should either wait for the config server nodes to fully replicate the data or keep looping the mongos refresh until it is able to detect the sessions collection on the config server. 

      Edit: Another(better) solution would be to move the cache refresh when starting up a ShardingTest above this line to guarantee that each of the config server nodes has refreshed their cache.

            Assignee:
            sanika.phanse@mongodb.com Sanika Phanse (Inactive)
            Reporter:
            jason.zhang@mongodb.com Jason Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.