-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
v8.0, v7.0, v6.0
-
Cluster Scalability 2024-09-02
The write concern timeout for refreshing the sessions collection should be increased to 60 seconds from 15 seconds. This can help mitigate issues where longer replication lags can prevent the sessions collection from refreshing which then causes an accumulation of sessions in memory. I think changing the timeout should be okay because I saw that the value of 15 seconds was arbitrarily chosen a few years ago.
- is related to
-
SERVER-94001 Make LogicalSessionCacheRefresh more resilient to errors from a single shard
- Backlog
- related to
-
SERVER-94635 Make session refresh parameters configurable
- Closed