[SERVER-50366] StorageTimestampTests::TimestampIndexBuilds<true> fails when resumable index builds are enabled Created: 18/Aug/20 Updated: 29/Oct/23 Resolved: 18/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| 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 2020-08-24 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The TimestampIndexBuilds<true> test case in the StorageTimestampTests dbtest suite fails on this IndexBuildsCoordinator invariant when resumable index builds are enabled. The underlying error embedded in the invariant message is a ReadConcernMajorityNotAvailableYet error from the WiredTigerSnapshotManager. The underlying issue may be related to changes to the collection scan phase introduced in This has to be resolved before resumable index builds can be enabled by default in |
| Comments |
| Comment by Githook User [ 18/Aug/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |