[DOCS-14655] Slight correction of Initial Sync Semantics downgrade docs Created: 16/Jul/21  Updated: 13/Nov/23  Due: 23/Jul/21  Resolved: 20/Jul/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Andrew Feierabend (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 2 years, 29 weeks, 1 day ago
Epic Link: DOCSP-15042
Story Points: 2

 Description   

I noticed that https://docs.mongodb.com/v5.0/release-notes/5.0-downgrade-sharded-cluster/#5.-downgrade-feature-compatibility-version--fcv- says "Ensure that no nodes have a newlyAdded field in their replica set configuration. Use the rs.conf() method on each node in your sharded cluster to verify this. The newlyAdded only appears in a node's replica set configuration document during and shortly after an initial sync."

rs.conf() would omit newlyAdded fields due to SERVER-46353. Users who would like to see any ‘newlyAdded’ fields can do so by querying the ‘local.system.replset’ collection directly.



 Comments   
Comment by Githook User [ 20/Jul/21 ]

Author:

{'name': 'andf-mongodb', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}

Message: DOCS-14655 correct newlyAdded downgrade step
Branch: master
https://github.com/mongodb/docs/commit/cc5817371e38b745345e463fe22acc013714552b

Comment by Andrew Feierabend (Inactive) [ 19/Jul/21 ]

Thank you.

Comment by Judah Schvimer [ 19/Jul/21 ]

Sure! I think the correct code example would be:

use local
db.system.replset.find( { "members.newlyAdded" : { $exists : true } } );

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