error UnexpectedWriteType("CAS")) with multiple tokio tasks about cdrs-tokio HOT 10 CLOSED

Can you check with protocol v4?

from cdrs-tokio.

Do you mean downgrade to an old Cassandra? or is there a way to make it fall back to the older protocol?

from cdrs-tokio.

You can specify the protocol version when building connection configuration: https://docs.rs/cdrs-tokio/7.0.0/cdrs_tokio/cluster/struct.NodeTcpConfigBuilder.html#method.with_version

from cdrs-tokio.

It happens with V3, V4 and V5. Less often in the older protocol versions.

from cdrs-tokio.

Also, wanted to mention that this is an LWT batch. The code in question is here: https://gitlab.com/lightning-signer/validating-lightning-signer/-/merge_requests/312/diffs#144ee5d06667bb53830287a66cd0bda0b514e40c_0_319 (look for async fn put if I push again and invalidate the line locator)

from cdrs-tokio.

The scylla driver gives me a more detailed error: Scylla(QueryError(DbError(WriteTimeout { consistency: Serial(LocalSerial), received: 1, required: 2, write_type: Cas }, "Operation timed out - received only 1 responses.")))'

So cdrs is probably getting confused by the write_type on this error.

Well, I'm confused by this error myself...

from cdrs-tokio.

If you're getting it on a two different drivers, it means a problem in your cluster.

from cdrs-tokio.

agreed. however, the cdrs driver does eat part of the error - would be good to fix.

from cdrs-tokio.

Sure, I'll take a look.

from cdrs-tokio.

This turns out to be a braking change and will be included in the next major version.

• Add remaining options from https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v5.spec#L1289
• Remove Copy from WriteType
• Add UnknownWriteType(String) variant
• Add non_exhaustive

from cdrs-tokio.