Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mongodb.org/v2.6/core/replica-set-oplog/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36
*Referrer*: https://docs.mongodb.org/v2.6/reference/glossary/
*Screen Resolution*: 1920 x 1200
*repo*: docs
*source*: core/replica-set-oplog
*Location*: https://docs.mongodb.org/v2.6/core/replica-set-oplog/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36 *Referrer*: https://docs.mongodb.org/v2.6/reference/glossary/ *Screen Resolution*: 1920 x 1200 *repo*: docs *source*: core/replica-set-oplog
Description
In the v2.6 manual (https://docs.mongodb.org/v2.6/core/replica-set-oplog/#oplog-status), under the "Oplog Status" section:
the printReplicationInfo() method is called on the rs object, when it should be called on the db object.
Patch:
- rs.printReplicationInfo()
+ db.printReplicationInfo()