Direct deletes to a shard might throw an StaleShardVersion exception (introduced in SERVER-61847). Under that scenario, the TTL Monitor logs an error but it doesn't recover the shard version. Thus, if there are no other operations, the next time that TTL task is executed it will also fail.
- causes
-
SERVER-63530 TTL Monitor should not log an error message on StaleShardVersion errors
- Closed
-
SERVER-63567 Flag the ttl_monitor_recovers_shard_version.js with the requires_persistence flag
- Closed
- is caused by
-
SERVER-61847 Handle direct updates/deletes to shards that modify orphan docs
- Closed
- related to
-
SERVER-58036 TTL monitor can delete documents during chunk migration's and resharding's critical sections
- Closed