DATACASS-656 - Increase test timeouts to run safely on slower environments.
This commit is contained in:
@@ -15,6 +15,27 @@ datastax-java-driver {
|
||||
class = DcInferringLoadBalancingPolicy
|
||||
}
|
||||
|
||||
basic.request {
|
||||
# How long the driver waits for a request to complete. This is a global limit on the duration of
|
||||
# a session.execute() call, including any internal retries the driver might do.
|
||||
#
|
||||
# By default, this value is set pretty high to ensure that DDL queries don't time out, in order
|
||||
# to provide the best experience for new users trying the driver with the out-of-the-box
|
||||
# configuration.
|
||||
# For any serious deployment, we recommend that you use separate configuration profiles for DDL
|
||||
# and DML; you can then set the DML timeout much lower (down to a few milliseconds if needed).
|
||||
#
|
||||
# Note that, because timeouts are scheduled on the driver's timer thread, the duration specified
|
||||
# here must be greater than the timer tick duration defined by the
|
||||
# advanced.netty.timer.tick-duration setting (see below). If that is not the case, timeouts will
|
||||
# not be triggered as timely as desired.
|
||||
#
|
||||
# Required: yes
|
||||
# Modifiable at runtime: yes, the new value will be used for requests issued after the change.
|
||||
# Overridable in a profile: yes
|
||||
timeout = 8 seconds
|
||||
}
|
||||
|
||||
# ADVANCED OPTIONS -------------------------------------------------------------------------------
|
||||
|
||||
advanced.connection {
|
||||
|
||||
Reference in New Issue
Block a user