[SERVER-39981] modify StorageTimestampTests::InitialSyncSetIndexMultikeyOnInsert to build indexes in foreground Created: 06/Mar/19  Updated: 29/Oct/23  Resolved: 06/Mar/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Task 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
related to SERVER-39982 modify StorageTimestampTests::Initial... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-03-11
Participants:
Linked BF Score: 10

 Description   

In recent weeks, the test StorageTimestampTests::InitialSyncSetIndexMultikeyOnInsert has been failing intermittently with the following invariant message:

[repl-index-builder-1] Invariant failure !mySnapshot || *mySnapshot <= commitTimestamp commit timestamp Timestamp(1, 87) cannot be older than current read timestamp Timestamp(1, 92) src/mongo/db/catalog/index_timestamp_helper.cpp 88

Since the intent of the test case is not to test background/hybrid builds, it should be fine to have this test build its indexes in the foreground until we get a better understanding why this test is not interacting well with background/hybrid index builds.

A TODO comment in the code should mention SERVER-39982.



 Comments   
Comment by Githook User [ 06/Mar/19 ]

Author:

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

Message: SERVER-39981 StorageTimestampTests::InitialSyncSetIndexMultikeyOnInsert builds indexes in the foreground
Branch: master
https://github.com/mongodb/mongo/commit/d0265ef8ba219d8ebaf703bcec45ab232fd90024

Generated at Thu Feb 08 04:53:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.