Also, it never seems to put a packet on the wire. An lcb_remove with durability set to none looks like:
But, if it is set to anything else, I don't see a delete request on the wire at all, and the request times out. Interestingly, a subsequent lcb_remove without durability set, for that same id, also times out (using the same lcb instance). In fact, everything times out on this instance after asking for a durable remove. And, seems nothing goes out on wire as well. I still see the instance's cluster config calls, Audit Put, etc...
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
CB robot April 27, 2021 at 6:58 AM
Build couchbase-server-7.0.0-5043 contains libcouchbase commit 495e039 with commit message: : fix protocol magic for durable remove
David Kelly March 12, 2021 at 5:59 PM
Since transactions should be during durable remove when upstaging (and I found this by trying to fix a bug where we were not doing so), calling critical as the proper functioning of transactions relies on it.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Also, it never seems to put a packet on the wire. An
lcb_removewith durability set to none looks like:But, if it is set to anything else, I don't see a delete request on the wire at all, and the request times out. Interestingly, a subsequent lcb_remove without durability set, for that same id, also times out (using the same lcb instance). In fact, everything times out on this instance after asking for a durable remove. And, seems nothing goes out on wire as well. I still see the instance's cluster config calls, Audit Put, etc...