Critical Description
Also, it never seems to put a packet on the wire. An lcb_remove with durability set to none looks like:
Frame 548: 117 bytes on wire (936 bits), 117 bytes captured (936 bits) on interface lo0, id 0
|
Null/Loopback
|
Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1
|
Transmission Control Protocol, Src Port: 60648, Dst Port: 11210, Seq: 783, Ack: 15570, Len: 61
|
Couchbase Protocol, Delete Request, Opcode: 0x4, VBucket: 0x37
|
Magic: Request (0x80)
|
Opcode: Delete (0x04)
|
Key Length: 37
|
Extras Length: 0
|
Data Type: 0x00
|
.... ...0 = JSON: Not set
|
.... ..0. = Snappy: Not set
|
.... .0.. = XATTR: Not set
|
VBucket: 55 (0x0037)
|
[Value Length: 0]
|
Total Body Length: 37
|
Opaque: 0x00000005
|
CAS: 0x0000000000000000
|
Key:
|
[Expert Info (Warning/Undecoded): Trailing stray characters]
|
[Trailing stray characters]
|
[Severity level: Warning]
|
[Group: Undecoded]
|
Collection ID: 0x00000000
|
Collection Logical Key: 769229bc-d3da-4b64-aead-9f2be0b81015
|
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...