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

Creates a new instance of WriteFailureException.

Determines whether the specified object is equal to the current object.

When overridden in a derived class, returns the Exception that is the root cause of one or more subsequent exceptions.

Serves as the default hash function.

When overridden in a derived class, sets the SerializationInfo with information about the exception.

Gets the runtime type of the current instance.

Creates and returns a string representation of the current exception.

Gets the consistency level of the operation

Gets a collection of key/value pairs that provide additional user-defined information about the exception.

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

Gets or sets a link to the help file associated with this exception.

Gets or sets HRESULT, a coded numerical value that is assigned to a specific exception.

Gets the Exception instance that caused the current exception.

Gets a message that describes the current exception.

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 or sets the name of the application or the object that causes the error.

Gets a string representation of the immediate frames on the call stack.

Gets the method that throws the current exception.

Gets the type of write operation that timed out.

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