[SERVER-24545] Replicaset secondary abnormal exit. Created: 14/Jun/16  Updated: 06/Dec/22  Resolved: 09/Aug/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.7
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Jagger Wang Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-25160 Drain and catchup modes shouldn't con... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

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.



 Comments   
Comment by Eric Milkie [ 09/Aug/16 ]

I'm going to resolve this ticket as a duplicate; please follow the linked ticket for updates on the fix to this issue (SERVER-25160). Thanks for reporting this!

Comment by Jagger Wang [ 17/Jun/16 ]

Uploaded, files are mongod.log-20160614-primary and mongod.log-20160614-secondary.

Comment by Kelsey Schubert [ 17/Jun/16 ]

Thank you, jaggerwang. Please use this secure portal to upload the logs.

Kind regards,
Thomas

Comment by Jagger Wang [ 17/Jun/16 ]

Ok, you can give me upload portal, I'll give you the full log of that day, it's about 50 MB.

Comment by Kelsey Schubert [ 16/Jun/16 ]

Hi jaggerwang,

I've examined the logs you have provided. Unfortunately, there is not enough information to determine the root cause of this issue.

  • Would you please attach the full logs for each member in the replicaset? If needed, I can provide an upload portal for you to use.

I see that your secondary is reporting

2016-06-14T02:06:12.978+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { create_time: -1.0 }, name: "create_time_-1", ns: "message.taobao_message", background: true, expireAfterSeconds: 2592000 } -- 28556 Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.028+0800 I -        [TTLMonitor] Assertion: 28556:Didn't find RecordId in WiredTigerRecordStore

This assertion may be indicative of index corruption. To get a better idea of what is going on here, would you please provide the output of the following commands against the affected secondary, please note that db.collection.validate(true) is a resource intensive operation and may impact the performance of the secondary.

rs.slaveOk()
var c=db.getSisterDB("message").taobao_message;
assert.eq(c.distinct("_id").length); 
c.count());
c.validate(true);

Finally, I would recommend upgrading to MongoDB 3.0.12 or MongoDB 3.2.7 which include a number of fixes which may improve the behavior of your replica set.

Thank you,
Thomas

Comment by Jagger Wang [ 14/Jun/16 ]

Output of rs.conf():

xd-offline:PRIMARY> rs.conf()
{
	"_id" : "xd-offline",
	"version" : 5,
	"members" : [
		{
			"_id" : 0,
			"host" : "xd-jst2:27017",
			"arbiterOnly" : false,
			"buildIndexes" : true,
			"hidden" : false,
			"priority" : 1,
			"tags" : {
 
			},
			"slaveDelay" : 0,
			"votes" : 1
		},
		{
			"_id" : 1,
			"host" : "xd-jst5:27022",
			"arbiterOnly" : false,
			"buildIndexes" : true,
			"hidden" : false,
			"priority" : 2,
			"tags" : {
 
			},
			"slaveDelay" : 0,
			"votes" : 1
		},
		{
			"_id" : 2,
			"host" : "xd-jst5:27023",
			"arbiterOnly" : true,
			"buildIndexes" : true,
			"hidden" : false,
			"priority" : 1,
			"tags" : {
 
			},
			"slaveDelay" : 0,
			"votes" : 1
		}
	],
	"settings" : {
		"chainingAllowed" : true,
		"heartbeatTimeoutSecs" : 10,
		"getLastErrorModes" : {
 
		},
		"getLastErrorDefaults" : {
			"w" : 1,
			"wtimeout" : 0
		}
	}
}

Primary log:

2016-06-14T02:06:09.641+0800 I REPL     [ReplicationExecutor] replSet possible election tie; sleeping 977ms until 2016-06-14T02:06:10.618+0800
2016-06-14T02:06:10.618+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:10.620+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:10.620+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:10.622+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst2:27017
2016-06-14T02:06:10.622+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:10.622+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:11 2016 before standing for election again
2016-06-14T02:06:11.455+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:11.457+0800 I REPL     [ReplicationExecutor] replSet possible election tie; sleeping 1040ms until 2016-06-14T02:06:12.497+0800
2016-06-14T02:06:12.497+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:12.500+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:12.500+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:12.502+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst2:27017
2016-06-14T02:06:12.502+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:12.502+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:12 2016 before standing for election again
2016-06-14T02:06:12.700+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:12.702+0800 I REPL     [ReplicationExecutor] replSet possible election tie; sleeping 310ms until 2016-06-14T02:06:13.012+0800
2016-06-14T02:06:13.012+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:13.014+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:13.014+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:13.016+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:13.018+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:13.018+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:14.126+0800 I NETWORK  [conn3153827] end connection 10.117.11.192:45103 (58 connections now open)
2016-06-14T02:06:14.128+0800 I NETWORK  [initandlisten] connection accepted from 10.117.11.192:45113 #3153828 (59 connections now open)
2016-06-14T02:06:14.768+0800 I REPL     [ReplicationExecutor] syncing from: xd-jst2:27017
2016-06-14T02:06:14.827+0800 I REPL     [SyncSourceFeedback] replset setting syncSourceFeedback to xd-jst2:27017
2016-06-14T02:06:15.017+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:15.017+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:15.017+0800 I REPL     [ReplicationExecutor] not electing self, we are not freshest
2016-06-14T02:06:15.561+0800 I NETWORK  [conn3153765] end connection 10.117.11.192:45048 (58 connections now open)
2016-06-14T02:06:15.561+0800 I NETWORK  [conn3153772] end connection 10.117.11.192:45054 (57 connections now open)
2016-06-14T02:06:15.731+0800 E REPL     [rsBackgroundSync] sync producer problem: 10278 dbclient error communicating with server: xd-jst2:27017
2016-06-14T02:06:15.753+0800 I NETWORK  [SyncSourceFeedback] Socket recv() errno:104 Connection reset by peer 10.117.11.192:27017
2016-06-14T02:06:15.753+0800 I NETWORK  [SyncSourceFeedback] SocketException: remote: 10.117.11.192:27017 error: 9001 socket exception [RECV_ERROR] server [10.117.11.192:27017]
2016-06-14T02:06:15.753+0800 I NETWORK  [SyncSourceFeedback] DBClientCursor::init call() failed
2016-06-14T02:06:15.754+0800 I REPL     [SyncSourceFeedback] SyncSourceFeedback error sending handshake: DBClientBase::findN: transport error: xd-jst2:27017 ns: admin.$cmd query: { replSetUpdatePosition: 1, handshake: { handshake: ObjectId('56db94ec2945ecb002deee24'), member: 0, config: { _id: 0, host: "xd-jst2:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } } }
2016-06-14T02:06:15.758+0800 I -        [rsBackgroundSync] caught exception (socket exception [FAILED_STATE] for xd-jst2:27017 (10.117.11.192) failed) in destructor (kill)
2016-06-14T02:06:15.759+0800 I REPL     [ReplicationExecutor] could not find member to sync from
2016-06-14T02:06:15.971+0800 I NETWORK  [ReplExecNetThread-7445] DBClientCursor::init call() failed
2016-06-14T02:06:15.971+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location10276 DBClientBase::findN: transport error: xd-jst2:27017 ns: admin.$cmd query: { replSetHeartbeat: "xd-offline", pv: 1, v: 5, from: "xd-jst5:27022", fromId: 1, checkEmpty: false }
2016-06-14T02:06:15.971+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:15.974+0800 W NETWORK  [ReplExecNetThread-7460] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:15.974+0800 W NETWORK  [ReplExecNetThread-7445] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:15.974+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:15.977+0800 W NETWORK  [ReplExecNetThread-7460] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:15.977+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:15.993+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:15.993+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:15.993+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:15.993+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:16 2016 before standing for election again
2016-06-14T02:06:16.695+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:16.696+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:16.702+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:16.702+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:16.702+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:17 2016 before standing for election again
2016-06-14T02:06:17.216+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:17.217+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:17.217+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:17.217+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:17.217+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:17 2016 before standing for election again
2016-06-14T02:06:17.426+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:17.427+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:17.427+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:17.427+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:17.427+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:17 2016 before standing for election again
2016-06-14T02:06:17.557+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:17.557+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:17.558+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:17.558+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:17.558+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:17 2016 before standing for election again
2016-06-14T02:06:17.848+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:17.848+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:17.848+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:17.848+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:17.848+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:18 2016 before standing for election again
2016-06-14T02:06:17.979+0800 W NETWORK  [ReplExecNetThread-7445] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:17.979+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:17.982+0800 W NETWORK  [ReplExecNetThread-7460] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:17.982+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:17.984+0800 W NETWORK  [ReplExecNetThread-7461] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:17.984+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:18.573+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:18.573+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:18.574+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:18.574+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:18.574+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:18 2016 before standing for election again
2016-06-14T02:06:18.946+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:18.946+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:18.947+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:18.947+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:18.947+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:19 2016 before standing for election again
2016-06-14T02:06:19.022+0800 I REPL     [ReplicationExecutor] Standing for election
2016-06-14T02:06:19.022+0800 I REPL     [ReplicationExecutor] replSet info electSelf
2016-06-14T02:06:19.022+0800 I REPL     [ReplicationExecutor] received vote: 0 votes from xd-jst5:27023
2016-06-14T02:06:19.022+0800 I REPL     [ReplicationExecutor] replSet couldn't elect self, only received 1 votes, but needed at least 2
2016-06-14T02:06:19.022+0800 I REPL     [ReplicationExecutor] waiting until Tue Jun 14 02:06:20 2016 before standing for election again
2016-06-14T02:06:19.986+0800 W NETWORK  [ReplExecNetThread-7460] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:19.986+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:19.988+0800 W NETWORK  [ReplExecNetThread-7461] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:19.988+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed
2016-06-14T02:06:19.990+0800 W NETWORK  [ReplExecNetThread-7445] Failed to connect to 10.117.11.192:27017, reason: errno:111 Connection refused
2016-06-14T02:06:19.990+0800 I REPL     [ReplicationExecutor] Error in heartbeat request to xd-jst2:27017; Location18915 Failed attempt to connect to xd-jst2:27017; couldn't connect to server xd-jst2:27017 (10.117.11.192), connection attempt failed

Secondary log:

2016-06-14T02:06:10.621+0800 I REPL     [ReplicationExecutor] replSet voting no for xd-jst5:27022; voted for xd-jst2:27017 17 secs ago
2016-06-14T02:06:12.501+0800 I REPL     [ReplicationExecutor] replSet voting no for xd-jst5:27022; voted for xd-jst2:27017 18 secs ago
2016-06-14T02:06:12.738+0800 I -        [TTLMonitor] Assertion: 28556:Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:12.966+0800 I CONTROL  [TTLMonitor]
2016-06-14T02:06:12.978+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { create_time: -1.0 }, name: "create_time_-1", ns: "message.taobao_message", background: true, expireAfterSeconds: 2592000 } -- 28556 Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.028+0800 I -        [TTLMonitor] Assertion: 28556:Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.037+0800 I CONTROL  [TTLMonitor]
2016-06-14T02:06:13.037+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { create_time: -1.0 }, name: "create_time_-1", ns: "xdmp.order", background: true, expireAfterSeconds: 604800 } -- 28556 Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.066+0800 I -        [TTLMonitor] Assertion: 28556:Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.095+0800 I CONTROL  [TTLMonitor]
2016-06-14T02:06:13.096+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { create_time: 1.0 }, name: "create_time_1", ns: "xdmp_log.log", background: true, expireAfterSeconds: 604800.0 } -- 28556 Didn't find RecordId in WiredTigerRecordStore
2016-06-14T02:06:13.116+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { uploadDate: -1 }, name: "uploadDate_-1", ns: "xdms_offline.clienterror.bindata", expireAfterSeconds: 1209600, background: false } -- 20 cannot remove from a capped collection: xdms_offline.clienterror.bindata
2016-06-14T02:06:13.142+0800 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { uploadDate: -1 }, name: "uploadDate_-1", ns: "xdms_offline.corpuserror.bindata", expireAfterSeconds: 1209600, background: false } -- 20 cannot remove from a capped collection: xdms_offline.corpuserror.bindata
2016-06-14T02:06:14.726+0800 I NETWORK  [conn2301386] end connection 10.132.181.246:39043 (58 connections now open)
2016-06-14T02:06:14.728+0800 I NETWORK  [initandlisten] connection accepted from 10.132.181.246:39056 #2301449 (59 connections now open)
2016-06-14T02:06:14.752+0800 I ACCESS   [conn2301449] Successfully authenticated as principal __system on local
2016-06-14T02:06:14.772+0800 I NETWORK  [initandlisten] connection accepted from 10.132.181.246:39057 #2301450 (60 connections now open)
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]

Comment by Kelsey Schubert [ 14/Jun/16 ]

Hi jaggerwang,

Thank you for opening this ticket. So we can continue to investigate this issue would you please provide the following information?

  1. Complete logs for each member of the replica set
  2. Output of rs.conf()

Thank you,
Thomas

Generated at Thu Feb 08 04:06:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.