-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.0.6
-
Component/s: Sharding
-
None
-
Environment:MongoDB version 2.0.6
The following mongos 2.0.6 stack trace appears to have occurred when a shard hit its connection limit:
Thu Jul 19 21:55:48 [Balancer] DBClientCursor::init call() failed Received signal 11 Backtrace: 0x54e5b5 0x7f20b429d900 0x585f03 0x588061 0x5888bd 0x756723 0x756eab 0x75c402 0x7dbbd4 0x7dc15f 0x52503f 0x5273b4 0x8069e0 0x7f20b4da27f1 0x7f20b4350ccd mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x54e5b5] /lib64/libc.so.6(+0x32900)[0x7f20b429d900] mongos(_ZN5mongo17ReplicaSetMonitor16_checkConnectionEPNS_18DBClientConnectionERSsbi+0x1543)[0x585f03] mongos(_ZN5mongo17ReplicaSetMonitorC1ERKSsRKSt6vectorINS_11HostAndPortESaIS4_EE+0x381)[0x588061] mongos(_ZN5mongo17ReplicaSetMonitor3getERKSsRKSt6vectorINS_11HostAndPortESaIS4_EE+0x1fd)[0x5888bd] mongos(_ZN5mongo5Shard7_rsInitEv+0x133)[0x756723] mongos(_ZN5mongo5Shard8_setAddrERKSs+0x13b)[0x756eab] mongos(_ZN5mongo15StaticShardInfo6reloadEv+0xab2)[0x75c402] mongos(_ZN5mongo8Balancer5_initEv+0x44)[0x7dbbd4] mongos(_ZN5mongo8Balancer3runEv+0x3f)[0x7dc15f] mongos(_ZN5mongo13BackgroundJob7jobBodyEN5boost10shared_ptrINS0_9JobStatusEEE+0xbf)[0x52503f] mongos(_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi3mf1IvN5mongo13BackgroundJobENS_10shared_ptrINS7_9JobStatusEEEEENS2_5list2INS2_5valueIPS7_EENSD_ISA_EEEEEEE3runEv+0x74)[0x5273b4] mongos(thread_proxy+0x80)[0x8069e0] /lib64/libpthread.so.0(+0x77f1)[0x7f20b4da27f1] /lib64/libc.so.6(clone+0x6d)[0x7f20b4350ccd] ===
The relevant code is in client/dbclient_rs.cpp. Determine if this is a bug, and if it has already been fixed for 2.2.
- is duplicated by
-
-
- Closed
-