[SERVER-44344] legacy map reduce fails to recreate indexes in existing output collection with two phase index builds Created: 31/Oct/19 Updated: 29/Oct/23 Resolved: 04/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 | ||||||||
| Sprint: | Execution Team 2019-11-04 | ||||||||
| Participants: | |||||||||
| Description |
|
When given an output collection that already exists, the map reduce command will copy the indexes from the original output collection. With two phase index builds, the information in the startIndexBuild and commitIndexBuild oplog entries may contain indexes that already exist in the temporary collection used by map reduce. This may result in secondaries silently ignoring the two phase index build commands due to the IndexAlreadyExists error. |
| Comments |
| Comment by Githook User [ 02/Nov/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 01/Nov/19 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: |