public class ReadFailureException extends QueryConsistencyException
This happens when some of the replicas that were contacted by the coordinator replied with an error.
This exception is processed by
CoordinatorException, int), which will decide if it is rethrown directly to the client or if the
request should be retried. If all other tried nodes also fail, this exception will appear in the
AllNodesFailedException thrown to the client.
|Constructor and Description|
|Modifier and Type||Method and Description|
Copy the exception.
Returns the number of replicas that experienced a failure while executing the request.
Returns the a failure reason code for each node that failed.
Whether the actual data was amongst the received replica responses.
getBlockFor, getConsistencyLevel, getReceived
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public int getNumFailures()
public boolean wasDataPresent()
During reads, Cassandra doesn't request data from every replica to minimize internal network traffic. Instead, some replicas are only asked for a checksum of the data. A read failure may occur even if enough replicas have responded to fulfill the consistency level, if only checksum responses have been received. This method allows to detect that case.
@NonNull public Map<InetAddress,Integer> getReasonMap()
At the time of writing, the existing reason codes are:
0x0000: the error does not have a specific code assigned yet, or the cause is unknown.
0x0001: The read operation scanned too many tombstones (as defined by
cassandra.yaml, causing a
This feature is available for protocol v5 or above only. With lower protocol versions, the map will always be empty.
@NonNull public DriverException copy()
This returns a new exception, equivalent to the original one, except that because a new object is created in the current thread, the top-most element in the stacktrace of the exception will refer to the current thread. The original exception may or may not be included as the copy's cause, depending on whether that is deemed useful (this is left to the discretion of each implementation).
This is intended for the synchronous wrapper methods of the driver, in order to produce a more user-friendly stack trace (that includes the line in the user code where the driver rethrew the error).
Copyright © 2017–2020. All rights reserved.