Hi, 

We have a collection with a TTL index set to expire documents after 0 seconds, resulting in the deletion of over 100,000 documents. This aggressive deletion is causing disk saturation. To mitigate this, we set ttlMonitorEnabled: false on the primary server to stop further deletion, but deletions continue across the cluster.

*

*

1. Set ttlMonitorEnabled: false on the primary server to halt TTL deletions.
2. Despite this change, TTL deletions persist cluster-wide.

We believe this behavior may indicate a bug in the TTL monitor's functionality. plz help on this 

System

OS: Amazon Linux 2 (aarch64)
MongoDB Version: 7.0.14