Details
-
Bug
-
Resolution: Incomplete
-
Major - P3
-
None
-
1.6.1, 1.6.3
-
None
-
None
-
mongodb 1.6.3, php_mongo 1.0.7
servers:
- srv1 = Debian Lenny. kernel 2.6.26-2-amd64 #1 SMP x86_64 GNU/Linux. CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz RAM: 16GB
- srv2 = Debian Lenny. kernel 2.6.26-2-openvz-amd64 #1 SMP x86_64 GNU/Linux under openvz 3.0.23-1dso1 with no limit. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz RAM: 16GB
replicaset:
- master on srv1:27017
- arbiter on srv1:30001
- slave on srv2mongodb 1.6.3, php_mongo 1.0.7 servers: - srv1 = Debian Lenny. kernel 2.6.26-2-amd64 #1 SMP x86_64 GNU/Linux. CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz RAM: 16GB - srv2 = Debian Lenny. kernel 2.6.26-2-openvz-amd64 #1 SMP x86_64 GNU/Linux under openvz 3.0.23-1dso1 with no limit. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz RAM: 16GB replicaset: - master on srv1:27017 - arbiter on srv1:30001 - slave on srv2
-
Linux
Description
We have encountered strange behavior of MongoDB during a rapid increase in requests for data retrieval. Record queue and the number of connections begin to grow rapidly. The results of db.currentOp () are attached to the ticket. What else can we check and how to do this? What are the collections "?" in the list of operations for? And what is mean sign "?" in first position of namespace?