Details
-
Task
-
Resolution: Duplicate
-
Major
-
None
-
None
-
2
-
SDK34, SDK36
Description
Opening this per team discussion because .NET team thinks this problem that was first noticed in LCB will probably effect .NET as well, and requires investigation. Please upgrade from Task to Bug and update the description if confirmed.
See linked CBSE-14831 and CCBC-1607 for additional details, but Sergey provided the following reproduction steps:
- setup two node cluster with KV service with 6.6 version
- add one 7.1 node
- rebalance
- bootstrap libcouchbase using 7.1 node
- libcouchbase will get socket configured for collections, because kv engine from 7.1 node will ack collection support
- libcouchbase then receive configuration, and sees that the config does not have "collections" capability and disables collections support for whole lcb_INSTANCE
- send GET command, and libcouchbase will not add zero prefix for default collection
- kv engine tries to interpret first byte of the key as a collection index, and returns COLLECTION_NOT_FOUND9. libcouchbase silently retries expecting that this is just cold collection, that will be accessible in a moment10. application gets timeout error