[CSHARP-391] Change default value of SocketTimeout to let the OS set its own default (presumably infinite) Created: 13/Feb/12 Updated: 02/Apr/15 Resolved: 13/Feb/12 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | None |
| Affects Version/s: | 1.3.1 |
| Fix Version/s: | 1.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Stam | Assignee: | Robert Stam |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Description |
|
Currently the default value for SocketTimeout is 30 seconds. This is too low for some kinds of long running operations (like Map/Reduce). Instead of having any default value the C# driver will simply let the OS use its own defaults, which normally means infinite. If the application writer wants to set a default they can, in which case they are in a position to know what a good default value for their use case would be. |
| Comments |
| Comment by Craig Wilson [ 22/Nov/13 ] |
|
That is a different timeout, related to how long we wait to connect. The socket timeout is applied here and here in MongoConnection. |
| Comment by Mark Gibaud [ 22/Nov/13 ] |
|
@Robert Am I incorrectly assuming that the C# driver ignores the setTimeout setting anyway? |
| Comment by Robert Stam [ 13/Feb/12 ] |
|
Only breaking if you were counting on the timeout. |