-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: SAMUS
-
None
-
Environment:Win32
Using MongoDB-CSharp driver to carryout a MapReduce on a collection of 1M documents leads to a network connection timeout.
The mapreduce does run to completion but a timeout exception is displayed in the driver. [Chaning the timeout from default to 120 still leads to a timeout.]
Is this a problem with the db? Should it immediately return? With the client polling for progress?
Or is there an issue with driver?