-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
cheahuychou.mao@mongodb.com gave some suggestions on how we could do this:
- For logicalSessionRefreshMillis (i.e. the period for the jobs), we could do that by adding an on_update observer to it that would update the period for the jobs based on the new value (e.g. here and here).
- For disableLogicalSessionCacheRefresh, we could do that by adding an on_update observer to it that would pause / resume the jobs based on the new value.