Major Description
At least, according to the RFC. But, there isn't a lcb_cmdping_timeout to set it on a per-request basis. Also – I periodically see that some endpoints timed out in the json, but the request didn't seem to wait very long - could be the timeout isn't the KV default by default? Not sure.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 3.0.1 [ 16708 ] |
| Status | New [ 10003 ] | Open [ 1 ] |
| Fix Version/s | 3.0.2 [ 16717 ] | |
| Fix Version/s | 3.0.1 [ 16708 ] |
| Description | At least, according to the RFC. I'm not sure what should happen exactly when the timeout is exceeded -- should we just get an error? Or do we see the others that responded in time, plus some indication that there were other services that didn't respond? And I guess that would need to be reflected in the json that we get back from {{lcb_respping_value}} (vs iterating with k{{lcb_respping_result_service}}) | At least, according to the RFC. But, there isn't a {{lcb_cmdping_timeout}} to set it on a per-request basis. Also -- I periodically see that some endpoints timed out in the json, but the request didn't seem to wait very long - could be the timeout isn't the KV default by default? Not sure. |
| Story Points | 1 |
| Fix Version/s | 3.0.3 [ 16778 ] | |
| Fix Version/s | 3.0.2 [ 16717 ] |
| Component/s | docs [ 10111 ] |
| Component/s | library [ 10110 ] | |
| Component/s | docs [ 10111 ] |
| Fix Version/s | 3.0.4 [ 16919 ] | |
| Fix Version/s | 3.0.3 [ 16778 ] | |
| Labels | ping |
| Fix Version/s | 3.0.5 [ 17057 ] | |
| Fix Version/s | 3.0.4 [ 16919 ] |
| Fix Version/s | 3.0.6 [ 17114 ] | |
| Fix Version/s | 3.0.6 [ 17114 ] | |
| Fix Version/s | 3.0.5 [ 17057 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Build couchbase-server-7.0.0-4433 contains libcouchbase commit 354a15b with commit message:
CCBC-1175: ping: allow to specify timeout for command