Currently, Atlas has a "Kill Op" option which is useful to kill single long-running queries. When upgrading to MongoDB 7.0, we were faced with a situation where the Slot-Based Query Engine (SBE) was causing 1000s of queries to execute slowly, we wanted to kill them all, but it was more than a human could do by clicking "Kill Op" 1-by-1. Hence a "Mass Kill" feature which kills queries longer than X seconds (X is configurable) would have helped us greatly in an outage scenario. We ultimately rebooted our cluster to kill queries, then manually implemented a script which did this from the MongoDB console. We would need ability to do this on both primary and secondary nodes. Related requests: - https://feedback.mongodb.com/forums/924145-atlas/suggestions/43772352-killallsessionsbypattern-and-kill-sessions - https://feedback.mongodb.com/forums/924145-atlas/suggestions/42420421-allow-db-killop-and-manual-restarts-on-secondari