-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 3.0.7
-
Component/s: Replication
-
None
-
Replication
-
ALL
The mongod log as follows:
2016-06-14T02:06:14.824+0800 I ACCESS [conn2301450] Successfully authenticated as principal __system on local
2016-06-14T02:06:14.831+0800 I NETWORK [initandlisten] connection accepted from 10.132.181.246:39058 #2301451 (61 connections now open)
2016-06-14T02:06:14.855+0800 I ACCESS [conn2301451] Successfully authenticated as principal __system on local
2016-06-14T02:06:15.150+0800 F REPL [rsSync] replication oplog stream went back in time. previous timestamp: 575ef615:3e3 newest timestamp: 575ef614:1. Op being applied: { ts: Timestamp 1465841172000|1, h: -8349955578268963721, v: 2, op: "d", ns: "xd_stat.mssa_log", b: true, o: { _id: ObjectId('57554af5652ca43487b96f88') } }
2016-06-14T02:06:15.150+0800 I - [rsSync] Fatal Assertion 18905
2016-06-14T02:06:15.151+0800 I - [rsSync]
***aborting after fassert() failure
Mongodb version 3.0.7 on Ubuntu 12.04. The replicaset is running about six months, everything is ok, until today. After restart, service is ok.
- duplicates
-
-
- Closed
-