Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.1.0-dp1, 1.1.0-dp2, 1.1.0-dp3, 1.1.0-dp4, 1.1.0-dp5
-
Fix Version/s: 1.1.0
-
Component/s: None
-
Security Level: Public
-
Labels:None
Description
Since the server side view timeout is 60s, we should raise the client side a bit higher. 75s seems like the right number.
It must also be tuneable through the constructor to the client or the .ini file or both.
It must also be tuneable through the constructor to the client or the .ini file or both.
Activity
Matt Ingenthron
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Raise view timeout from 60s to 75s | make default view timeout 75s |
| Description | Since the server side view timeout is 60s, we should raise the client side a bit higher. 75s seems like the right number. It should be tuneable though. |
Since the server side view timeout is 60s, we should raise the client side a bit higher. 75s seems like the right number.
It must also be tuneable through the constructor to the client or the .ini file or both. |
Trond Norbye
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Matt Ingenthron
made changes -
| Fix Version/s | 1.1.0 [ 10242 ] | |
| Fix Version/s | 1.1.0-dp6 [ 10402 ] |
Matt Ingenthron
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
For what it's worth, it wouldn't hurt my feelings if we were to create a second timeout in libcouchbase for http requests. Maybe there is one already? The only problem with that is that the API/ABI in libcouchbase is required to be stable for now (since we hit Beta).