[DOCS-1876] Update entry for printSlaveReplicationInfo() Created: 02/Sep/13  Updated: 04/Mar/23  Resolved: 07/May/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.6
Fix Version/s: v1.3.5, mongodb-2.6

Type: Improvement Priority: Minor - P4
Reporter: Daniel Pasette (Inactive) Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: sprint-rollover
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-7800 Fix "db.printSlaveReplicationInfo()" ... Closed
Participants:
Days since reply: 9 years, 40 weeks, 5 days ago

 Description   

There were some improvements to the output in 2.5.1. See SERVER-7800.

Should give example output here:
http://docs.mongodb.org/manual/reference/method/db.printSlaveReplicationInfo/

Also, need to update example here and improve description which says 'syncedTo value is last optime read.' It's actually the last oplog entry written to the secondary:
http://docs.mongodb.org/manual/tutorial/troubleshoot-replica-sets/#check-the-replication-lag



 Comments   
Comment by Githook User [ 09/May/14 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-1876: trivial tweak. Since rs.printSlaveReplicationInfo calls db.printSlaveReplicationInfo, adding same note about delayed member
Branch: master
https://github.com/mongodb/docs/commit/8a72870fa821c942e45fe71009fe095e23d8ad2e

Comment by Githook User [ 09/May/14 ]

Author:

{u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}

Message: DOCS-1876: Update entry for printSlaveReplicationInfo()

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/80bdb8aad7c6329f7957291c0f851875c4cfee03

Comment by Asya Kamsky [ 14/Dec/13 ]

Probably important to highlight that a delayed slave may be showing 0 seconds behind primary when inactivity period on primary is greater than slaveDelay.

On systems where there are periods of inactivity delayed secondary may also appear more than "delay interval" behind the primary.

I.e. 600 seconds slaveDelay.

time primary event secondary event secondary shows delay
t0 insert1   0 and climbing
t300 insert2   300 and climbing
t600 insert3 insert1 600 and dropping
t900   insert2 300 to 600 and dropping
t1200   insert3 300 to 600 then dropping to 0
      if there are no more events in the next 60s

slaveDelay will appear to be between 0 and 599 seconds depending on when you check.

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