If the suite did not specify this setting, it will be overwritten with value of 1 secs here or here). This can make it more susceptible to SERVER-87673. This is because we allow cursors to live even after stepdowns which has a effect of "unpinning" the sharding metadata of the cursor from the range deleter since the range deleter on the new primary will have no knowledge about the cursors on the older primary.
- is related to
-
SERVER-95713 Re-set orphanCleanupDelaySecs in suites with balancer and failovers
- Closed
- related to
-
SERVER-77354 Increase the value of orphanCleanupDelaySecs for concurrency_sharded_causal_consistency_and_balancer
- Closed
-
SERVER-92251 Set orphanCleanupDelaySecs in concurrency_sharded_with_stepdowns_and_balancer_and_config_transitions.yml
- Closed