- 
    Type:Task 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: Sharding
- 
        Fully Compatible
- 
        Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
indexed_insert_where.js performs finds with $where, which are not very performant. This can cause failures when running on the concurrency_sharded_causal_consistency_and_balancer suite: This suite does secondary reads. In case of find on a secondary that runs longer than orphanCleanupDelaySecs, the range deleter could kick in before the query on the secondary has finished and remove the documents the query expected to find. (SERVER-31934 has some more context about this issue on that suite).
Since indexed_insert_where.js is know to run 'finds' that could take longer than the default orphanCleanupDelaySecs in our tests (1 second), we should not run this test on the concurrency_sharded_causal_consistency_and_balancer suite.
- is depended on by
- 
                    SERVER-43099 Reenable random chunk migration failpoint for concurrency with_balancer suites -         
- Closed
 
-         
- is related to
- 
                    SERVER-77354 Increase the value of orphanCleanupDelaySecs for concurrency_sharded_causal_consistency_and_balancer -         
- Closed
 
-