Issue Description
We are encountering an unhandled memcached error (0x8 - NO_BUCKET) when attempting to retrieve a document from Couchbase. The issue appears intermittently, and resetting Couchbase connections does not resolve it.
INFO - Reusing server server-node-cb-5.xxxxx:11210 (0x7ff46400b0e0). OldIndex=6. NewIndex=6
ERROR - Got unhandled memcached error 0x8
WARN - server-node-cb-5.xxxxx:11210 (CTX=0x7ff464001480,memcached,SRV=0x7ff46403fc10,IX=2)
Received server error NO_BUCKET (0x8) on packet: OP=0xbb, RC=0x8, SEQ=2
ERROR - Error in getting data from Couchbase:
“A generic / unknown error happened: {"collection":"_default","status":8,
"key":"ACT_TT_6522221a-8037-4a04-97df-fxxxf398b46a1","opaque":2,
"bucket":"cb_bucket","scope":"_default",
"remote":"server-node-cb-5.xxxxx:11210"}”
INFO - Resetting Couchbase connections
INFO - Version=3.0.3, Changeset=0xdeadbeef
INFO - Requested network configuration: heuristic
INFO - Requesting connection to node server-node-cb-5.xxxxx:11210 for CCCP configuration `
Yes this does look like the same issue, but is there any other way as the plans for the rust sdk were changed midway and in the end we are obliged to use the alpha version of the sdk which doesn’t have wait_until_ready method
For reference this is our connection string:
let mut connection_url = couchbase://host-1,host-2,host-3,host-4?operation_timeout=60
We store the cluster and bucket connections globally and reuse them
We have also added additional retry with timeout logic inside the code for errors
Can you suggest an alternate way to handle this or something that maybe we are missing?
Hello ,
We were resetting the cluster and bucket connections when retrying on an error, and apparently by removing the cluster reset logic and only resetting bucket connection worked.
Thanks for helping!