[SERVER-46745] Failed to update config.system.sessions collection from the config shard primary Created: 10/Mar/20  Updated: 08/Jan/24  Resolved: 08/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.2.1, 4.2.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Duplicate Votes: 0
Labels: KP42
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-42827 Allow sessions collection to return O... Closed
Duplicate
duplicates SERVER-42827 Allow sessions collection to return O... Closed
Related
Operating System: ALL
Backport Requested:
v4.4, v4.2
Sprint: Sharding 2020-04-06, Sharding 2020-04-20
Participants:
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



 Comments   
Comment by Eric Sedor [ 13/Apr/20 ]

Adding this duplication link to make it clearer that the fix is tracked there (SERVER-42827)

Comment by Kaloian Manassiev [ 13/Mar/20 ]

misha.tyulenev, can you please add a bit more detail about why is the config.system.sessions collection not updated specifically from the primary of the config server? And also what are the customer-visible effects of this?

Generated at Thu Feb 08 05:12:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.