Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
6.6.6
-
1
Description
This MB tries to address the corner cases in which, after a failover, query does not ditch old data node or pick up new data nodes, and insists in picking up non responsive nodes in error.
Attachments
Issue Links
- backports to
-
-
- Closed
-
| For Gerrit Dashboard: MB-53950 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 182720,3 | MB-53950 initial commit | cheshire-cat | query | Status: MERGED | +2 | +1 |
| 182721,3 | MB-53950 initial commit | cheshire-cat | go-couchbase | Status: MERGED | +2 | +1 |
Activity
Build couchbase-server-7.0.5-7658 contains go-couchbase commit fb66b75 with commit message:
MB-53950 initial commit
Build couchbase-server-7.0.5-7658 contains query commit bfc889f with commit message:
MB-53950 initial commit
There might be an extra improvement that could be done, but I haven't even tried it on master, let alone back ported it, so we'll probably leave it for 7.0.6.
Build couchbase-server-7.0.6-8007 contains go-couchbase commit fb66b75 with commit message:
MB-53950 initial commit
Build couchbase-server-7.0.6-8007 contains query commit bfc889f with commit message:
MB-53950 initial commit
Here's a list of defects that have made changes relevant to mad hatter connection management issues.
Again, let's have it on record that these would require a major rewrite of go-couchbase and datastore/couchbase/couchbase.go on both 7.0 and 6.6 and they are not simple cherry picks.
Some do have descriptions that are completely unrelated to failures to detect vbmap changes, but do have code changes that apply.
On that vein, in many cases, it's not the whole fix that needs to be applied, but selected code.
MB-39370MB-41065MB-41980MB-42753MB-44019MB-44328MB-45048MB-50172MB-50725I cannot exclude to have missed a few.
Overall, it may work better to go through datastore/couchbase/couchbase.go and the primitives package, and amend the earlier code from the newer fixes.