[DOCS-9753] 3.4 Release notes inaccurately state: rs.status() output to report on initial sync status and progress Created: 10/Jan/17  Updated: 04/Jan/23  Resolved: 28/Jun/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eric Sommer Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-8598 Add initial sync progress information... Closed
Participants:
Days since reply: 4 years, 32 weeks, 5 days ago

 Description   

https://docs.mongodb.com/master/release-notes/3.4/#improved-initial-sync

Modified rs.status() output to report on initial sync status and progress.

Turns out (as per DOCS-8598) that to get the initial sync info, you need to run:

db.runCommand({replSetGetStatus: 1, initialSync: 1})

Since rs.status() wraps vanilla command

db.runCommand({ replSetGetStatus: 1 })

, it does not return the initial sync information.



 Comments   
Comment by Kay Kim (Inactive) [ 28/Jun/19 ]

Heh – forgot to close it from a while back.

commit on 3.4:

https://github.com/mongodb/docs/commit/59f81eb460ebc11bc80cacf1ab1718f51dd27c01

Comment by Judah Schvimer [ 11/Jan/17 ]

I'm not so familiar with that syntax, though in my testing that doesn't work. It would need to wrap:

db.adminCommand({replSetGetStatus: 1, initialSync: 1})

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