Details
-
Bug
-
Status: Backlog
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
Sharding NYC
-
ALL
-
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
-
(copied to CRM)
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.
Attachments
Issue Links
- is duplicated by
-
SERVER-46982 localLogicalSessionTimeoutMinutes does not affect lsidTTLIndex
-
- Closed
-
- is related to
-
SERVER-37624 Sessions never expire when you change value of localLogicalSessionTimeoutMinutes
-
- Closed
-
- related to
-
SERVER-46982 localLogicalSessionTimeoutMinutes does not affect lsidTTLIndex
-
- Closed
-