[SERVER-43218] lsidTTLIndex is incorrect after modifying localLogicalSessionTimeoutMinutes in sharded cluster Created: 06/Sep/19  Updated: 17/Nov/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James Kovacs Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
Duplicate
is duplicated by SERVER-46982 localLogicalSessionTimeoutMinutes do... Closed
Problem/Incident
Related
related to SERVER-46982 localLogicalSessionTimeoutMinutes do... Closed
is related to SERVER-37624 Sessions never expire when you change... Closed
Assigned Teams:
Cluster Scalability
Operating System: ALL
Sprint: Sharding 2019-10-07, Sharding 2019-10-21, Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13
Participants:
Case:

 Description   

If you create a sharded cluster running MongoDB 3.6 or later, the config server primary will create a sharded collection config.system.sessions with a TTL index lsidTTLIndex with an expiresAfterSeconds set to localLogicalSessionTimeoutMinutes x 60. If you later restart all cluster nodes with a new localLogicalSessionTimeoutMinutes, the TTL indexes on the shards is not updated to the new value. If you drop the lsidTTLIndex, it will be recreated with the correct value.


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