When mapReduce and killOp operations are executed concurrently, a race condition occurs, resulting in two mapReduce operations running at the same time and targeting the same output collection. This happens because killOp may not terminate mapReduce, leading to either continued execution and the initiation of another mapReduce process after acknowledging the interruption.

The objective of this ticket is to resolve this test issue.