The test runs concurrent mapReduce commands with output mode "replace" against the same target collection. Since "replace" involves dropping the target collection as part of the final rename operation, there's a small window where a mapReduce starts after the target is dropped and not yet renamed. If this happens, the second MR will fail on it's final rename due to this assertion.