-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.4.8, 2.4.9
-
Component/s: Replication
-
Labels:None
-
ALL
I've resynced this server several times but keep getting something like the following:
***** SERVER RESTARTED *****
Sun Mar 16 16:02:24.567 [websvr] admin web console waiting for connections on port 28017
Sun Mar 16 16:02:30.714 [rsStart] replSet I am m4.example.com:27017
Sun Mar 16 16:02:36.716 [rsStart] replSet STARTUP2
Sun Mar 16 16:02:36.721 [rsHealthPoll] replSet member m5.example.com:27017 is up
Sun Mar 16 16:02:36.721 [rsHealthPoll] replSet member m5.example.com:27017 is now in state PRIMARY
Sun Mar 16 16:02:37.717 [rsSync] replSet still syncing, not yet to minValid optime 5325bf2f:1f
Sun Mar 16 16:02:38.724 [rsHealthPoll] replSet member a1..example.com:27017 is up
Sun Mar 16 16:02:38.724 [rsHealthPoll] replSet member a1.incrowdads.net:27017 is now in state ARBITER
Sun Mar 16 16:02:38.849 [rsHealthPoll] replSet member m8.example.com:27017 is up
Sun Mar 16 16:02:38.849 [rsHealthPoll] replSet member m8.example.com:27017 is now in state SECONDARY
Sun Mar 16 16:02:43.718 [rsBackgroundSync] replSet syncing to: m5.example.com:27017
Sun Mar 16 16:02:43.719 [rsSync] replSet still syncing, not yet to minValid optime 5325bf2f:1f
Sun Mar 16 16:02:43.969 [rsBackgroundSync] replSet our last op time fetched: Mar 16 15:11:34:2c
Sun Mar 16 16:02:43.969 [rsBackgroundSync] replset source's GTE: Mar 16 15:11:39:1
Sun Mar 16 16:02:43.969 [rsBackgroundSync] replSet need to rollback, but in inconsistent state
Sun Mar 16 16:02:43.969 [rsBackgroundSync] minvalid: 5325bf2f:1f our last optime: 5325bf26:2c
Sun Mar 16 16:02:43.969 [rsBackgroundSync] replSet FATAL
What's happening here? What other information do I need to look at to make sense of this?
- is related to
-
SERVER-7200 use oplog as op buffer on secondaries
-
- Closed
-