[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: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 40 weeks, 5 days ago | ||||||||
| Description |
|
There were some improvements to the output in 2.5.1. See Should give example output here: 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: |
| 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: | ||||||||||||||||||||||||||||
| 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: Signed-off-by: kay <kay.kim@10gen.com> | ||||||||||||||||||||||||||||
| 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.
slaveDelay will appear to be between 0 and 599 seconds depending on when you check. |