From b083941b7c944a9859596214f755127b73a25da1 Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Thu, 12 Dec 2019 16:24:44 +0100 Subject: [PATCH] DATACASS-656 - Increase test timeouts to run safely on slower environments. --- .../src/test/resources/application.conf | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/spring-data-cassandra/src/test/resources/application.conf b/spring-data-cassandra/src/test/resources/application.conf index d4e2494a2..0c06ac827 100644 --- a/spring-data-cassandra/src/test/resources/application.conf +++ b/spring-data-cassandra/src/test/resources/application.conf @@ -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 {