[SERVER-43439] Make movePrimary wait for updates from the database refresh to be written before clearing the flag in the minOpTimeRecovery document Created: 23/Sep/19  Updated: 29/Oct/23  Resolved: 15/Jan/20

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

Type: Task Priority: Major - P3
Reporter: PM Bot Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: autogen-todo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-32608 Make secondaries refresh their databa... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-13, Sharding 2020-01-27
Participants:

 Comments   
Comment by Githook User [ 14/Jan/20 ]

Author:

{'name': 'Janna Golden', 'email': 'janna.golden@mongodb.com', 'username': 'jannaerin'}

Message: SERVER-43439 Remove TODO to add call to waitForDatabaseFlush
Branch: master
https://github.com/mongodb/mongo/commit/5f36cc7f2f02807966bbd0b0b70b255ac502e1ff

Comment by Esha Maharishi (Inactive) [ 03/Jan/20 ]

Making movePrimary wait for the updates from the database refresh to be persisted before clearing the inMigration flag is real work that should have been implemented.

The logic should mirror the waitForCollectionFlush call in the MigrationSourceManager.

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