-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.0
-
Component/s: Sharding
-
None
-
Environment:linux
-
ALL
-
Mongos consumes 14g+ of the 16g physical memory, smaps file is attached.
The behavior is very similar to that of https://jira.mongodb.org/browse/SERVER-6354 and https://jira.mongodb.org/browse/SERVER-6785 , but both have been resolved before 2.4.0.
Detail of mongos version:
$mongos --version
MongoS version 2.4.0 starting: pid=31557 port=27017 64-bit host=xxxx (--help for usage)
git version: ce2d666c04b4a80af58e8bbb3388b0680e8cfeb6
build sys info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49
$ ldd mongos
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003f18800000)
librt.so.1 => /lib64/librt.so.1 (0x0000003f1c800000)
libstdc+.so.6 => /usr/lib64/libstdc+.so.6 (0x0000003f1bc00000)
libm.so.6 => /lib64/libm.so.6 (0x0000003f18400000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003f1b800000)
libc.so.6 => /lib64/libc.so.6 (0x0000003f17c00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003f16c00000)
- is related to
-
SERVER-8720 Memory leak in DBClientReplicaSet::slaveConn
- Closed
-
SERVER-9139 cursor leak in mongos of unsharded cursors
- Closed