public class NodeUnavailableException extends DriverException
Node
was selected in a query plan, but it had no connection available.
A common reason to encounter this error is when the configured number of connections per node and requests per connection is not high enough to absorb the overall request rate. This can be mitigated by tuning the following options:
advanced.connection.pool.local.size
;
advanced.connection.pool.remote.size
;
advanced.connection.max-requests-per-connection
.
reference.conf
for more details.
Another possibility is when you are trying to direct a request to a particular node, but that node has no connections available.
Constructor and Description |
---|
NodeUnavailableException(Node node) |
Modifier and Type | Method and Description |
---|---|
DriverException |
copy()
Copy the exception.
|
Node |
getNode() |
getExecutionInfo, setExecutionInfo
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public NodeUnavailableException(Node node)
@NonNull public Node getNode()
@NonNull public DriverException copy()
DriverException
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).
copy
in class DriverException
Copyright © 2017–2024. All rights reserved.