When runnign db.printReplicationInfo() from the mongo shel, it returns unreal dates:
MongoDB shell version: 2.4.0
connecting to: admin
rs3:SECONDARY> db.printReplicationInfo()
configured oplog size: 150000MB
log length start to end: 431.84499999997206secs (0.12hrs)
oplog first event time: Fri Jan 16 1970 18:45:42 GMT+0000 (UTC)
oplog last event time: Fri Jan 16 1970 18:52:54 GMT+0000 (UTC)
now: Fri Mar 22 2013 17:49:06 GMT+0000 (UTC)
When connecting from a 2.2 client shell, it returns the correct dates:
MongoDB shell version: 2.2.2
connecting to: rs1-***.***.com/admin
rs3:SECONDARY> db.printReplicationInfo()
configured oplog size: 150000MB
log length start to end: 431751secs (119.93hrs)
oplog first event time: Sun Mar 17 2013 17:50:30 GMT+0000 (UTC)
oplog last event time: Fri Mar 22 2013 17:46:21 GMT+0000 (UTC)
now: Fri Mar 22 2013 17:48:32 GMT+0000 (UTC)
- is duplicated by
-
SERVER-9348 printReplicationInfo doesn't agree with actual oplog timestamps
- Closed
-
SERVER-9317 db.printReplicationInfo() output has date issue
- Closed
-
SERVER-9119 An issue with oplog and a slave in MongoDB 2.4.1
- Closed