[SERVER-2050] Enables ScopedDbConnection to set the timeout. Created: 02/Nov/10 Updated: 29/May/12 Resolved: 30/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Kazuki Ohta | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Participants: |
| Description |
|
Hi, we're now integrating mongodb into our products using C++ driver. We noticed that the client sometimes gets blocked forever, when the server is in high load. To solve this problem, setting the client-side timeout seems good idea. I looked at the code, and DBClientConnection has timeout parameter for the constructor. But we cannot specify that parameter via ScopedDbConnection. Could you add that API? |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 30/Aug/11 ] |
|
fixed as part of |
| Comment by Masahiro Nakagawa [ 17/Mar/11 ] |
|
This suggestion is good idea It blocks our product. Currently, I apply resolving patch every time. |