Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.6.5, 7.0.0, 7.0.1, 7.0.2, 7.0.3
-
Triaged
-
1
-
Yes
-
KV March-22
Description
With the restriction of 200 char limit it is possible that upgrading a pre 6.6.5 cluster will fail where previously it would have passed.
The reason is that with a key length > 250 in a mcbp response can result in a disconnect and hence a rebalance failure. However it is possible to have a dcp connection name length > 200 without triggering the key length > 250 response issue.
See customer CBSE linked as an example case.
The fix is to remove the restriction by reverting the associated patch https://review.couchbase.org/c/kv_engine/+/114481
Attachments
Issue Links
For Gerrit Dashboard: MB-51513 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
172119,1 | MB-51513: Revert "MB-34280: Set max DCP name to 200 characters" | master | kv_engine | Status: ABANDONED | -1 | -1 |
172485,2 | MB-51513: Revert "MB-34280: Set max DCP name to 200 characters" | cheshire-cat | kv_engine | Status: MERGED | +2 | +1 |
172486,2 | MB-51513: Merge 'couchbase/cheshire-cat' into 'couchbase/neo' | neo | kv_engine | Status: MERGED | +2 | +1 |
172495,1 | MB-51513: Merge branch 'couchbase/cheshire-cat' into 'couchbase/neo' | neo | kv_engine | Status: MERGED | +2 | +1 |
172599,1 | Merge branch 'neo' | master | kv_engine | Status: ABANDONED | 0 | -1 |
172641,1 | Merge branch 'neo' into master | master | kv_engine | Status: MERGED | +2 | +1 |