[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:
Related
is related to SERVER-50360 ValidateStateTest::OpenCursorsOnAllIn... Closed
is related to SERVER-48476 resumable index build should use majo... Closed
is related to SERVER-49847 Turn on resumable index build feature... Closed
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 SERVER-48476.

This has to be resolved before resumable index builds can be enabled by default in SERVER-49847.



 Comments   
Comment by Githook User [ 18/Aug/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-50366 fix StorageTimestampTests for resumable index builds
Branch: master
https://github.com/mongodb/mongo/commit/8982a53c39f6e1a3f29a17f1877f2e85dd62b73f

Generated at Thu Feb 08 05:22:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.