-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.2, 2.1.1, 2.2.1
-
Component/s: Connectivity
-
None
-
Environment:Windows Server 2012, Mongodb 3.0.5 on Centos 7
Hi everyone
Last week I have installed 2.1.1.5 (we used old legacy driver before) and noticed following serious problem:
cursors do not get closed but getting iddle being stuck in RAM.
Just to compare: in mms monitoring before upgrade we had 500 cursors in the air and now we 13.5K and the number is growing. After it reaches the cursors limit all system crashes.
There are similar tickets:
https://jira.mongodb.org/browse/SERVER-19061
https://jira.mongodb.org/browse/SERVER-17364
but they speak about mongo version problem. I do not think that this is the problem by us since we have 3.05 for half a year already and we did not have it before. Anyway i decreased cursors timeout but it does not seem to help because the cursors number is constantly growing.
- is related to
-
CSHARP-1515 Queries using the Legacy API can leak connections resulting in TimeoutExceptions
- Closed