[SERVER-36391] Fassert that FCV is set at the end of initial sync Created: 01/Aug/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

It is important to know that FCV is set at the end of initial sync, since the behavior at the end of initial sync may vary depending on the FCV. 

Adding this invariant requires changing the initial syncer tests to explicitly set FCV.



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

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com'}

Message: SERVER-36391 Don't allow creation of TTL indexes in embedded.
Branch: master
https://github.com/mongodb/mongo/commit/dbf1808cb4a7def9066fcb95df32dc50da9bb449

Comment by Eric Milkie [ 07/Aug/18 ]

There is no real barrier to any team doing this work. It involves changing the initial syncer test, so knowledge of how that test framework operates is helpful.

Comment by Gregory McKeon (Inactive) [ 07/Aug/18 ]

milkie is there a barrier to the storage team doing this work?

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