[SERVER-34639] Background indexes on primaries should advance the minimumVisibleSnapshot when they begin Created: 24/Apr/18 Updated: 29/Oct/23 Resolved: 25/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.7.5 |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| 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: | Storage NYC 2018-05-07 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 56 | ||||||||||||||||
| Description |
|
Starting a background index build on a primary does not set the minimumVisibleSnapshot on the collection until the index build finishes. If a reader reads at a timestamp A before an index build timestamped for B, a reader may iterate through the indexes for a collection and reach this invariant. From
This should be changed for all background index builds, not just on secondaries. |
| Comments |
| Comment by Githook User [ 25/Apr/18 ] |
|
Author: {'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams', 'name': 'Louis Williams'}Message: |
| Comment by Judah Schvimer [ 24/Apr/18 ] |
|
The attached code review calls setMinimumVisibleSnapshot in an onCommit handler, so this will work nicely with |
| Comment by Spencer Brody (Inactive) [ 24/Apr/18 ] |