[SERVER-44397] index build continues to enforce constraints after failing over from primary to secondary Created: 04/Nov/19 Updated: 29/Oct/23 Resolved: 18/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-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Indexing constraints are currently determined (enforced on primary; relaxed on secondary) at the start of an index build and stay intact throughout the life of an index build. With |
| Comments |
| Comment by Githook User [ 17/Nov/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |