[SERVER-49774] Enable rollback testing for resumable index builds in the collection scan phase Created: 21/Jul/20 Updated: 29/Oct/23 Resolved: 02/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-08-10, Execution Team 2020-08-24, Execution Team 2020-09-07 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
After Original description: If a node goes into rollback during the collection scan of a resumable index build, the majority committed view gets zeroed out which causes the scan to throw ReadConcernMajorityNotAvailableYet. We then hit this invariant since we currently do not expect an index build to fail this way. |
| Comments |
| Comment by Githook User [ 02/Sep/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| Comment by Suganthi Mani [ 10/Aug/20 ] |
|
Response to my previous question - the index build collection started during STARTUP state doesn't use majority committed snapshot cursor. So, we can't get "ReadConcernMajorityNotAvailableYet" error. |
| Comment by Suganthi Mani [ 10/Aug/20 ] |
|
gregory.noma benety.goh, tess.avitabile raised a valid question while triaging for |
| Comment by Benety Goh [ 06/Aug/20 ] |
|
This ticket is on hold until |
| Comment by Benety Goh [ 21/Jul/20 ] |
|
One of the test cases added in |