GetCidByName fails with "Not connected to any bucket"
Description
If GetCidByName (GetCid operation) is routed to a non-kv node, then the following exception will be logged and thrown:
Environment
Couchbase Operator 2.2.1
Couchbase Server 7.0.2
1 data node, 1 index node
Running in AKS and accessing the couchbase cluster using external networking
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
Jeffry Morris December 1, 2021 at 8:26 PM
Edited
This is reproducible, although the exception is not an ObjectDisposedException:
I will fix this bug and then investigate the ObjectDisposedException originally reported.
Malcolm Learner November 29, 2021 at 8:15 PM
This issue occurs pretty reliably for us. It may be due to how our cluster is hosted in Kubernetes. Is there any additional information you would like from us beyond what has already been supplied here and in https://support.couchbase.com/hc/en-us/requests/42849?
Richard Ponton November 20, 2021 at 1:57 AM
I have been looking at this area of the code, but I don't have any estimate on a fix, yet. This is a timing issue, and those are fundamentally hard to reproduce and troubleshoot.
Matt Ingenthron November 16, 2021 at 7:39 PM
Hey , thanks for posting here additional info!
Note that if you need a fix prioritized, the route through that (if you're an Enterprise subscriber) is to contact Couchbase support. We do pay attention to comments on priority here too, but at an advisory level more than as meeting subscriber requests.
Malcolm Learner November 16, 2021 at 7:27 PM
Note that this issue only occurs when the Data service is segregated from Query/Index services.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
If GetCidByName (GetCid operation) is routed to a non-kv node, then the following exception will be logged and thrown: