As of filing this ticket, the test map_reduce_drop.js runs in:

1. concurrency
2. concurrency_multitenancy_replication_with_atlas_proxy
3. concurrency_replication
4. concurrency_replication_for_backup_restore
5. concurrency_replication_for_export_import
6. concurrency_replication_last_continuous_new_new_old
7. concurrency_replication_last_continuous_new_old_new
8. concurrency_replication_last_continuous_old_new_new
9. concurrency_replication_last_lts_new_new_old
10. concurrency_replication_last_lts_new_old_new
11. concurrency_replication_last_lts_old_new_new
12. concurrency_replication_with_replica_set_endpoint
13. concurrency_sharded_with_auto_bootstrap
14. concurrency_sharded_with_balancer_and_auto_bootstrap

While most of these are replication suites, there are two sharded suites as well, despite SERVER-77039's claim that the test is incompatible with sharded suites.

I've disabled map_reduce_drop.js from all sharding suites to maintain consistency with SERVER-77039's claim. Please verify if things have changed since then and that this test should instead be run on all sharded suites.

You can search for the TODO on this ticket number and get rid of the tag that disables this test from all sharding suites.

Please wait until SERVER-95023 has gone in before starting this work.