[SERVER-57465] remove_newly_added_field_after_finishing_initial_sync.js does not wait until the new configuration has been replicated Created: 04/Jun/21  Updated: 29/Oct/23  Resolved: 29/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.3, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Repl 2021-06-28, Repl 2021-07-12
Participants:
Linked BF Score: 28

 Description   

remove_newly_added_field_after_finishing_initial_sync.js currently doesn't wait until the new configuration has been replicated, before stepping up a secondary. This can cause the step up command to fail, if the secondary is still processing the reconfiguration.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 11/Aug/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-57465 remove_newly_added_field_after_finishing_initial_sync.js does not wait until the new configuration has been replicated
Branch: v5.0
https://github.com/mongodb/mongo/commit/3ad63191956190728ef36e10e8bb03e901c4ac35

Comment by Githook User [ 29/Jun/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-57465 remove_newly_added_field_after_finishing_initial_sync.js does not wait until the new configuration has been replicated
Branch: master
https://github.com/mongodb/mongo/commit/cc620e19d97094d805e87deb06d5c2a6106c8ece

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