This was reported by one of our customers; it happens under heavy load, during a performance test. I've not been able to reproduce it yet.
A statement is prepared for SELECT v FROM foobar WHERE k = ? (k and v are blobs). Then bound statements for various partition keys are executed. One of them fails with:
Upon further investigation (the customer applied a patch to generate more logs), it turns out that the PreparedId stored client-side has no metadata associated with it; therefore the EXECUTE request is sent with SKIP_METADATA = false; but the ROWS response returned by Cassandra has no metadata, hence the error.
I've observed the messages after deserialization, so that could be a bug in the serialization layer.