Details
-
Bug
-
Status: Reopened
-
Critical
-
Resolution: Unresolved
-
3.2.5
-
None
-
None
-
1
Description
All the bucket ops fails with LCB_TIMEOUT when collection specified not found.
2022-05-25T14:47:55.453+05:30 [Info] eventing-consumer [worker_test_0:/var/folders/hv/kx_3xt_16bv27mp88bvx4hy80000gn/T//127.0.0.1:9000_0_1452035700.sock:51528] [lcb,retryq L:164 I:651589169] Failing command (pkt=0x7fc619c26440, opaque=3, retries=31, now=86422156ms, spent=5000892us, status=0x88) requested error: LCB_ERR_TIMEOUT (201), from retry queue: LCB_ERR_TIMEOUT (201)
|
2022-05-25T14:48:00.661+05:30 [Info] eventing-consumer [worker_test_0:/var/folders/hv/kx_3xt_16bv27mp88bvx4hy80000gn/T//127.0.0.1:9000_0_1452035700.sock:51528] [lcb,retryq L:164 I:651589169] Failing command (pkt=0x7fc61b40e940, opaque=6, retries=31, now=86427363ms, spent=5002707us, status=0x88) requested error: LCB_ERR_TIMEOUT (201), from retry queue: LCB_ERR_TIMEOUT (201)
|
For collection/scope doesn't exist returning LCB_ERR_TIMEOUT will break the LCB_ERROR_IS_TRANSIENT since it will return true even if the code returned by kv is not retriable and application will end up retrying the request.
In eventing for now we fixed this by checking kv status code(lcb_errctx_kv_status_code) but we expect lcb to give more detailed error code when scope/collection doesn't exist.
Sergey Avseyev, Could you please take a look?