Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
1
Description
Couchbase Server 6.0.0 (possibly other versions as well?) will fail to rebalance if an existing DCP connection has a name that approaches the maximum key length of 250 bytes. The problem was reported with a name 238 bytes long. The exact trigger length is unknown, but reserving 100 bytes should be safe.
Attachments
Issue Links
- causes
-
CBES-128 Couchbase Server fails to rebalance if Elasticsearch connector is running
-
- Resolved
-
-
KAFKAC-148 Couchbase Server fails to rebalance if Kafka connector is running
-
- Resolved
-
- is duplicated by
-
CBES-145 Ensure ElastricSearch Connector does not generate DCP connection names that are no longer than allowed by memcached
-
- Resolved
-
-
JDCP-136 Ensure java-DCP-client does not generate DCP connection names that are no longer than allowed by memcached
-
- Resolved
-
-
KAFKAC-160 Ensure Kafka Connector does not generate DCP connection names that are no longer than allowed by memcached
-
- Resolved
-
- relates to
-
JDCP-137 Increase connection name limit from 148 bytes to 200 bytes
-
- Resolved
-
For Gerrit Dashboard: JDCP-126 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
109212,2 | JDCP-126 Rebalance fails because DCP connection name is too long | master | java-dcp-client | Status: MERGED | +2 | +1 |