[SERVER-54755] ephermeralForTest engine does not implement getLatestOplogTimestamp Created: 24/Feb/21  Updated: 29/Oct/23  Resolved: 25/Feb/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: Sharding-EMEA, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-54345 Check for leftover data on shard coll... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

1. Run any suite that uses a sharded cluster with the ephemeralForTest engine.

Sprint: Sharding 2021-03-08
Participants:
Linked BF Score: 0

 Description   

After the changes on SERVER-54345 we need to wait for a write to reach majority when creating the shard index before continuing, to prevent that a rollback ends up having a sharded collection without the shard key index on the primary shard. However, the ephemeralForTest engine does not implement getLatestOplogTimestamp, causing a consistent failure when running any sharded test when using that engine. We could use something like waitForWriteConcern to wait for majority.



 Comments   
Comment by Githook User [ 25/Feb/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-54755 Wait for majority write concern using repl_client_info
Branch: master
https://github.com/mongodb/mongo/commit/390139a35733d94d709a60b2558deab91281100d

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