[CSHARP-3885] [Unconfigurable] connection rate limiter in 2.13.x breaks existing applications Created: 30/Sep/21 Updated: 28/Oct/23 Resolved: 11/Jan/22 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | None |
| Fix Version/s: | 2.14.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Boris Dogadov |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | connections, pooling | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Hello! The resolution for the I would like to ask you to expose the MaxConnecting parameter so driver users can tune it to their liking and disable it. Thank you, |
| Comments |
| Comment by Boris Dogadov [ 11/Jan/22 ] |
|
Fixed in |
| Comment by Boris Dogadov [ 11/Jan/22 ] |
|
Thanks onyxmaster, closing. |
| Comment by Aristarkh Zagorodnikov [ 10/Jan/22 ] |
|
Since |
| Comment by Gian Maria Ricci [ 08/Nov/21 ] |
|
Thanks a lot, we reverted the driver and can confirm that with the latest version (12.4) application come back at full speed.
Thanks. |
| Comment by Boris Dogadov [ 08/Nov/21 ] |
|
Hi alkampfer, thank you for your report. |
| Comment by Gian Maria Ricci [ 05/Nov/21 ] |
|
Actually a large application I'm working into was completely wasted upgrading from 2.12 to 2.13.2 version of the driver. We have critical paths where lots of threads are upgrading a checkpoint collection. Randomly all those thread were blocked, and we experienced from our log that a single document upgrade took 10 seconds or more. I think that such impacting settings should left public to be changed by user of the driver, the risk of breaking existing code is enormous.
|
| Comment by Boris Dogadov [ 01/Oct/21 ] |
|
Thanks onyxmaster, |
| Comment by Aristarkh Zagorodnikov [ 01/Oct/21 ] |
|
Sure. Before the 2.13 (in fact, I manually bisected the 2.12->2.13 history and arrived at commit 59a1268d8c1fa905820d7789dd2f86b350dc7648, which is how I found out about |
| Comment by Boris Dogadov [ 30/Sep/21 ] |
|
Thanks onyxmaster for your question. Thanks. |
| Comment by Aristarkh Zagorodnikov [ 30/Sep/21 ] |
|
I do not think this should be a connection string-level parameter since it would practically invite people to set it incorrectly, but maybe add it to MongoDefaults as a settable property? |