[CSHARP-327] Issue with maximum document size limited by driver. Created: 16/Sep/11  Updated: 19/Oct/16  Resolved: 17/Sep/11

Status: Closed
Project: C# Driver
Component/s: SAMUS
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Lenny Granovsky Assignee: Robert Stam
Resolution: Won't Fix Votes: 0
Labels: document, limit, size
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows



 Description   

I use "samus / mongodb-csharp" driver and I found it has internal limit of 4Mb for document size despite new versions of DB support up to 16Mb. This needs to either fixed with different limit or allow external configuration for people who use older versions of DB.
This is an easy fix, please fix it ASAP - need it a lot.



 Comments   
Comment by Lenny Granovsky [ 10/Oct/11 ]

 
Thank you very much. It has solved the issue. I keep the v1.2, removed Connect/Disconnect and it just works.
 
I appreciate very quick response...
 
Best regards,
 
Lenny

Comment by Robert Stam [ 10/Oct/11 ]

If you are calling Disconnect you are probably running into this issue that exists in the 1.2 C# driver:

https://jira.mongodb.org/browse/CSHARP-333

There is a bug in Disconnect that causes the connection pool size to get out of sync which eventually results in the exception you are getting.

I recommend one of the following options:

1. Don't call Disconnect (there is rarely a good reason to call this method)
2. Wait for the 1.3 driver
3. Get the latest source code from github and build the driver yourself
4. Use the 1.1 driver (last resort)

Your easiest alternative is to just not call Disconnect.

Comment by Lenny Granovsky [ 10/Oct/11 ]

Hi Robert,

I went the recommended route and took your driver instead (v1.2). But unfortunately I ran into another issue. Spent few days, but could not resolve it. I would really appreciate if you can help me. My issue is very similar to this: http://stackoverflow.com/questions/7446528/mongodb-c-driver-doesnt-release-connections-then-errors
The only difference is that I finally came down to using single thread, but constant heavy load (~700 calls/sec). After 100 requests it comes back with "Timeout waiting for MongoConnection". The result is the same using 32 bit and 64 bit systems.
I do see that connections getting released after a while, but it takes few seconds instead of right after I call "mongoserver.Disconnect()" method. I do use mongoserver.Create(connectionString) as recommended. Do you have any suggestions for me?
 
Thank you,
 
Lenny

Comment by Robert Stam [ 17/Sep/11 ]

Hmmm... must be an obsolete link. We are about to begin work on LINQ, but at this point I can't really offer an accurate ETA.

Comment by Lenny Granovsky [ 17/Sep/11 ]

Hi Robert,
 
They have link to submit issues via your web-site. This is the reason I did so. I need to have the LINQ - that was the reason I went with samus driver. I know you have long plans to add support for LINQ - do you have a realistic estimate on when it can happen?

Best regards,

Lenny

From: Robert Stam (JIRA) <jira@mongodb.org>

Comment by Robert Stam [ 17/Sep/11 ]

This JIRA project is for the official C# driver from 10gen (although it was used for the samus driver a long time ago). You might be able to get some help with the samus driver by posting on mongodb-csharp Google group. Or you could switch to the official C# driver.

Generated at Wed Feb 07 21:36:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.