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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 4.2.1, 4.2.3
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Sharding 2020-04-06, Sharding 2020-04-20
    • Case:

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              misha.tyulenev Misha Tyulenev
              Reporter:
              misha.tyulenev Misha Tyulenev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: