[SERVER-44492] Use unique collections names in map_reduce_with_chunk_migrations.js concurrency test Created: 08/Nov/19 Updated: 29/Oct/23 Resolved: 11/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 11/Nov/19 ] |
|
Author: {'username': 'nzolnierzmdb', 'email': 'nicholas.zolnierz@mongodb.com', 'name': 'Nicholas Zolnierz'}Message: |