[SERVER-48476] resumable index build should use majority read cursor for collection scan Created: 28/May/20 Updated: 29/Oct/23 Resolved: 08/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Samyukta Lanka |
| 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-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
For resumable index builds, in order to ensure that we do not need to roll back any of the keys inserted into the sorter, the collection scan should start at a timestamp that has been majority committed. We will also need to ensure that the side writes table doesn't miss any writes. When we initially begin the collection scan, we must first install the side writes interceptor and then wait for the last oplog entry (the last entry that was not captured by the interceptor) to become majority committed, before establishing the snapshot to read the collection. |
| Comments |
| Comment by Githook User [ 08/Jul/20 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |
| Comment by Githook User [ 26/Jun/20 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |
| Comment by Githook User [ 26/Jun/20 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |