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

Failed to update config.system.sessions collection from the config shard primary

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.1, 4.2.3
    • Component/s: Sharding
    • ALL
    • v4.4, v4.2
    • Sharding 2020-04-06, Sharding 2020-04-20

      Logical sessions cache is maintained on each cluster node. The sessions expiration is managed by the lsidTTLIndex on config.system.sessions

      The following scenario exposes the bug when logical sessions cache on config primary fails to synchronize with the config.system.sessions
      1. create a 2 shard cluster, with enableTestCommands=true and disableLogicalSessionCacheRefresh=true.

      2. start a session on a config primary

      use config;
      db.runCommand({startSession:1});
      

      3. check that the sessions are created is in the logical cache

      use config;
      db.aggregate([{$listLocalSessions: {allUsers: true}}]);
      

      4. check that there are no sessions in the collection on the shard:
      5. force logical cache refresh:

      db.adminCommand({refreshLogicalSessionCacheNow:1 });
      

      6. check that there are still no sessions in the collections

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: