Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
1
Description
Right now the logic on how to select the refresher is very simplistic: if we loaded the original config over http, it will use http for refresh. If it loads through carrier it will use carrier for refresh.
Unfortunately, this is too simplistic: we might bootstrap off of a node in a MDS environment where there is no KV service enabled, but throughout the cluster there are. If it is a couchbase bucket and a modern cluster, it is more or less a given. Using http refresh has a couple limitations and should not be used if we can help it.
Attachments
For Gerrit Dashboard: JVMCBC-657 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
108211,4 | JVMCBC-657: Switch refresher selection logic to use the most effective one. | master | couchbase-jvm-core | Status: MERGED | +2 | +1 |