[CSHARP-1536] Cursor do not get closed Created: 17/Jan/16 Updated: 13/Apr/16 Resolved: 13/Apr/16 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.0.2, 2.1.1, 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Moshe Shperling | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2012, Mongodb 3.0.5 on Centos 7 |
||
| Issue Links: |
|
||||||||
| Description |
|
Hi everyone Last week I have installed 2.1.1.5 (we used old legacy driver before) and noticed following serious problem: 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. |
| Comments |
| Comment by Robert Stam [ 18/Jan/16 ] |
|
The underlying issue that was fixed in I'm pretty sure what you are seeing is just a different manifestation of the same problem. In your case it would appear that you are only partially consuming the results of the cursor. Since the client side cursor is not being properly disposed, the symptom is that the cursor continues to live on the server side. I have high confidence that the fix for The "timeout after 0ms" issue was actually a separate issue. The error message was incorrectly reporting "0ms" instead of the actual timeout value. |
| Comment by Moshe Shperling [ 18/Jan/16 ] |
|
Hi Craig |
| Comment by Craig Wilson [ 17/Jan/16 ] |
|
Hi Moshe, The cursor problem is related to the issue in Craig |