com.datastax.oss.driver.api.core

Class NodeUnavailableException

java.lang.Object

java.lang.Throwable

java.lang.Exception

java.lang.RuntimeException

com.datastax.oss.driver.api.core.DriverException

com.datastax.oss.driver.api.core.NodeUnavailableException

All Implemented Interfaces:

Serializable

public class NodeUnavailableException
extends DriverException

Indicates that a 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.

See 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.

See Also:

Serialized Form

Constructor Summary

Constructors

Constructor and Description
NodeUnavailableException(Node node)

Method Summary

Modifier and Type	Method and Description
DriverException	copy() Copy the exception.
Node	getNode()

Methods inherited from class com.datastax.oss.driver.api.core.DriverException

getExecutionInfo, setExecutionInfo

Methods inherited from class java.lang.Throwable

addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

NodeUnavailableException

public NodeUnavailableException(Node node)

Method Detail

getNode

@NonNull
public Node getNode()

copy

@NonNull
public DriverException copy()

Description copied from class: DriverException

Copy the exception.

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).

Specified by:

copy in class DriverException