public class BusyPoolException extends DriverException implements CoordinatorException
query plan
.
This exception is a symptom that the driver is experiencing a high workload. If it happens regularly on all hosts,
you should consider tuning one (or a combination of) the following pooling options:
PoolingOptions.setMaxRequestsPerConnection(HostDistance, int)
: maximum number of
requests per connection;PoolingOptions.setMaxConnectionsPerHost(HostDistance, int)
: maximum number of
connections in the pool;PoolingOptions.setMaxQueueSize(int)
: maximum number of enqueued requests before
this exception is thrown.Constructor and Description |
---|
BusyPoolException(InetSocketAddress address,
int queueSize) |
BusyPoolException(InetSocketAddress address,
long timeout,
TimeUnit unit) |
Modifier and Type | Method and Description |
---|---|
BusyPoolException |
copy()
Copy the exception.
|
InetSocketAddress |
getAddress()
The full address of the coordinator host that was contacted.
|
InetAddress |
getHost()
The coordinator host that was contacted.
|
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public BusyPoolException(InetSocketAddress address, int queueSize)
public BusyPoolException(InetSocketAddress address, long timeout, TimeUnit unit)
public InetAddress getHost()
CoordinatorException
getAddress().getAddress()
.getHost
in interface CoordinatorException
null
if the coordinator is not known.public InetSocketAddress getAddress()
CoordinatorException
getAddress
in interface CoordinatorException
null
if the coordinator is not known.public BusyPoolException copy()
DriverException
copy
in class DriverException