[SERVER-46982]  localLogicalSessionTimeoutMinutes does not affect lsidTTLIndex Created: 19/Mar/20  Updated: 23/Apr/20  Resolved: 23/Apr/20

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

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

Issue Links:
Depends
depends on SERVER-37624 Sessions never expire when you change... Closed
Duplicate
duplicates SERVER-43218 lsidTTLIndex is incorrect after modif... Backlog
Related
is related to SERVER-43218 lsidTTLIndex is incorrect after modif... Backlog
Operating System: ALL
Steps To Reproduce:

1. start mongod:

mongod --setParameter localLogicalSessionTimeoutMinutes=1 --setParameter logicalSessionRefreshMillis=1000

the logicalSessionRefreshMillis is overriden to force index recreation sooner than default Refresh interval of 5 min

The log will show

 
[LogicalSessionCacheRefresh] Failed to refresh session cache: Location13111: wrong type for field (expireAfterSeconds) long != int

verify that the timeout did not change:

use confg
db.system.sessions.getIndexes()

verify that the {expireAfterSecods}} value in {lsidTTLIndex}} is 1800. While its expected to be 60 with the new value of the parameter.

 

Participants:

 Description   

lsidTTLIndex on config.system.sessions is not recreated when localLogicalSessionTimeoutMinutes is set to non default


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