[SERVER-17046] FASSERT 18750 in rsBackgroundSync Created: 26/Jan/15  Updated: 28/Jan/15  Resolved: 28/Jan/15

Status: Closed
Project: Core Server
Component/s: Replication, WiredTiger
Affects Version/s: 3.0.0-rc6
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Alvin Richards (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16921 WT oplog bottleneck on secondary Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

benchrun.py --testFilter "daily" -f testcases/*
3 node replset

Participants:

 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



 Comments   
Comment by Daniel Pasette (Inactive) [ 26/Jan/15 ]

likely duplicate of SERVER-16921, but need to confirm

Generated at Thu Feb 08 03:43:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.