This is especially important on sharded clusters where users abort a query via their mongos connection, which only aborts the query on the client side, yet continues to run on each shard's mongod underneath. Having the ability to set a maxTimeMS by default would solve this.
This is especially important on sharded clusters where users abort a query via their mongos connection, which only aborts the query on the client side, yet continues to run on each shard's mongod underneath. Having the ability to set a maxTimeMS by default would solve this.