WriteFailureException Class

Creates a new instance of WriteFailureException providing the failure reasons dictionary.

Creates a new instance of WriteFailureException.

Gets the consistency level of the operation

Gets the number of nodes that experienced a failure while executing the request.

Gets a failure reason code for each node that failed.

On older protocol versions, an empty map and only the number of Failures is provided.

0x0000Unknown reason0x0001Too many tombstones read (as controlled by the yaml tombstone_failure_threshold option)0x0002The query uses an index but that index is not available (built) on the queried endpoint.0x0003The query writes on some CDC enabled tables, but the CDC space is full (CDC data isn't consumed fast enough). Note that this can only happen in Write_failure in practice, but the reasons are shared between both exception.0x0004Some failures (one or more) were reported to the replica "leading" a counter write. The actual error didn't occur on the node that sent this failure, it is is simply the node reporting it due to how counter writes work; the initial reason for the failure should have been logged on the actual replica on which the problem occured).0x0005The table used by the query was not found on at least one of the replica. This strongly suggest a query was done on either a newly created or newly dropped table with having waited for schema agreement first.0x0006The keyspace used by the query was not found on at least one replica. Same likely cause as for tables above.

Gets the number of replica that had acknowledged/responded to the operation

Gets the minimum number of replica acknowledgements/responses that were required to fulfill the operation.

Gets the type of write operation that timed out.

Possible values: SIMPLE, BATCH, BATCH_LOG, UNLOGGED_BATCH and COUNTER.