[SERVER-2486] mongos didn't failover and eventually crashed on replica set reconfig Created: 05/Feb/11  Updated: 12/Jul/16  Resolved: 10/Feb/11

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 1.7.5
Fix Version/s: 1.7.6

Type: Bug Priority: Major - P3
Reporter: David Mytton Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File mongos.log.tar.gz    
Operating System: Linux
Participants:

 Description   

Attempted a reconfig on a replica set and although it appeared to failover, when I attempted any queries it errored and then crashed.

reconfig on set 2 at 07:52:44
reconfig on set 1 at 07:56:32 (SERVER-2484)

Sat Feb 5 08:15:47 checking replica set: set1
Sat Feb 5 08:15:47 checking replica set: set2
Sat Feb 5 08:15:47 checking replica set: set3
Sat Feb 5 08:15:58 [mongosMain] dbexit: received signal 15 rc:0 received signal 15
Received signal 6
Backtrace: 0x52fc75 0x3027e302d0 0x3027e30265 0x3027e31d10 0x3027e6a84b 0x3027e7230f 0x3027e7276b 0x5052d0 0x506be4 0x69b480 0x302860673d 0x3027ed3f6d
/home/david/mongodb/latest/bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x52fc75]
/lib64/libc.so.6[0x3027e302d0]
/lib64/libc.so.6(gsignal+0x35)[0x3027e30265]
/lib64/libc.so.6(abort+0x110)[0x3027e31d10]
/lib64/libc.so.6[0x3027e6a84b]
/lib64/libc.so.6[0x3027e7230f]
/lib64/libc.so.6(cfree+0x4b)[0x3027e7276b]
/home/david/mongodb/latest/bin/mongos(_ZN5mongo13BackgroundJob7jobBodyEN5boost10shared_ptrINS0_9JobStatusEEE+0x150)[0x5052d0]
/home/david/mongodb/latest/bin/mongos(_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi3mf1IvN5mongo13BackgroundJobENS_10shared_ptrINS7_9JobStatusEEEEENS2_5list2INS2_5valueIPS7_EENSD_ISA_EEEEEEE3runEv+0x74)[0x506be4]
/home/david/mongodb/latest/bin/mongos(thread_proxy+0x80)[0x69b480]
/lib64/libpthread.so.0[0x302860673d]
/lib64/libc.so.6(clone+0x6d)[0x3027ed3f6d]
===



 Comments   
Comment by Eliot Horowitz (Inactive) [ 10/Feb/11 ]

This is related to ReplicaSetMonitor thread safety issues fixed in master.

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