Description
ClusterInfoCache api leveraged by Eventing to figure out active Data service nodes in the cluster, doesn't take into consideration if that all KV nodes have at least one vbucket active for bucket that Eventing is interested to open up either SDK handles or DCP streams.
Attachments
Issue Links
- relates to
-
MB-30394 Don't leverage outgoing KV node as connection string for SDK bootstrap
- Closed