[SERVER-43218] lsidTTLIndex is incorrect after modifying localLogicalSessionTimeoutMinutes in sharded cluster - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Backlog
Priority: Major - P3
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding NYC
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
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.

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

Activity

People

Assignee:: Backlog - Sharding NYC

Reporter:: James Kovacs

Participants:: Backlog - Sharding NYC, James Kovacs

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Dates

Created:: Sep 06 2019 10:40:03 PM UTC

Updated:: Dec 06 2022 02:48:33 AM UTC