Details
-
Bug
-
Status: Closed
-
Critical - P2
-
Resolution: Duplicate
-
3.0.0-rc6
-
None
-
Fully Compatible
-
ALL
-
Description
Problem
On the primary I see a number of network connection failures. On logs on the Secondary show the following
2015-01-24T19:33:06.467-0500 I REPL [ReplicationExecutor] syncing from: ip-10-93-7-23.ec2.internal:27017
|
2015-01-24T19:33:06.468-0500 W REPL [rsBackgroundSync] we are too stale to use ip-10-93-7-23.ec2.internal:27017 as a sync source
|
2015-01-24T19:33:06.468-0500 I REPL [ReplicationExecutor] could not find member to sync from
|
2015-01-24T19:33:06.468-0500 I REPL [rsBackgroundSync] replSet error RS102 too stale to catch up
|
2015-01-24T19:33:06.468-0500 I REPL [rsBackgroundSync] replSet our last optime : Jan 24 19:24:29 54c437bd:1023c
|
2015-01-24T19:33:06.468-0500 I REPL [rsBackgroundSync] replSet oldest available is Jan 24 19:25:28 54c437f8:36bd
|
2015-01-24T19:33:06.468-0500 I REPL [rsBackgroundSync] replSet See http://dochub.mongodb.org/core/resyncingaverystalereplicasetmember
|
2015-01-24T19:33:06.468-0500 I REPL [ReplicationExecutor] transition to RECOVERING
|
2015-01-24T19:33:22.471-0500 I REPL [ReplicationExecutor] syncing from: ip-10-93-7-23.ec2.internal:27019
|
2015-01-24T19:33:22.473-0500 I REPL [SyncSourceFeedback] replset setting syncSourceFeedback to ip-10-93-7-23.ec2.internal:27019
|
2015-01-24T19:33:22.474-0500 I REPL [rsBackgroundSync] replSet our last op time fetched: Jan 24 19:24:29:1023c
|
2015-01-24T19:33:22.474-0500 I REPL [rsBackgroundSync] replset source's GTE: Jan 24 19:24:31:46df
|
2015-01-24T19:33:22.474-0500 F REPL [rsBackgroundSync] replSet need to rollback, but in inconsistent state
|
2015-01-24T19:33:22.474-0500 I REPL [rsBackgroundSync] minvalid: 54c437f8:36bd our last optime: 54c437bd:1023c
|
2015-01-24T19:33:22.474-0500 I - [rsBackgroundSync] Fatal Assertion 18750
|
2015-01-24T19:33:22.474-0500 I - [rsBackgroundSync]
|
|
|
***aborting after fassert() failure
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-