Description
In http://docs.couchbase.com/developer/dotnet-2.1/view-queries.html the documentation says ConnectionTimeout is in seconds. In reality, it seems to be in milliseconds.
This leads to the problem when using this property and setting it to one hour (3600) we actually reduce the timeout from the default of 60 seconds to 3.6 seconds.
In addition, making this problem much worse, the missing data from the timeouted nodes do not raise any exception (at least by default) so that it is impossible to find out this bug in runtime - you just randomly receive incomplete data from the views, until someone by a chance will find out this issue.
We have to regenerate 15 Gb of data because we've found this bug too late.
Attachments
Issue Links
- duplicates
-
DOC-702 Add note to "About document expiration" regarding SDK differences in TTL format
-
- Closed
-