Expose configuration property for Cassandra's control queries timeout

[logicatmidod]

While trying to use spring-data-cassandra with 2.3.5.RELEASE when trying to connect to cassandra getting below error

Caused by: com.datastax.oss.driver.api.core.DriverTimeoutException: query 'SELECT * FROM system_schema.tables' timed out after PT2S

I have configured these properties still don't know why timeout is considered to be PT2S

spring:
  profiles:
    active: mockdata,standalone
  data:
    cassandra:
      request:
        timeout: 120000
      connect-timeout-millis: 10000
      read-timeout-millis: 10000
      connect-timeout: 10000
      read-timeout: 10000
      pool:
        pool-timeout: 10000
      connection:
        connect-timeout: 120000
        init-query-timeout: 120000

Also tried to use DriverConfigLoaderBuilderCustomizer as specified here https://stackoverflow.com/questions/61332483/spring-boot-2-3-0-m4-cassandra-and-ssl but not able to overwrite the time
but cant see DriverConfigLoaderBuilderCustomizer Bean being invoked at all any config I am missing that needs to be done.

[snicoll]

@logicatmidod all those properties with -millis at the end do not exist. I can only guess you were trying to make this work. If you have an IDE that has Spring Boot integration it should do a much better job at hinting you to that.

The property that you're looking to tune for the exception above is spring.data.cassandra.request.timeout. I can see it being set but that exception seems to indicate that it hasn't been. It is impossible for me to figure out why that is with the information you've shared.

If you want support, please take the time to build a small sample that we can run to reproduce the problem. You can do so by attaching a zip to this issue or sharing a link to a GitHub repository.

[logicatmidod]

I solved this issue by setting

advanced.control-connection.timeout

by setting manually at Datastax Driver Option this property was not exposed at spring boot side.
spring.data.cassandra.request.timeout is already set initially when it was not set I was facing some other timeout error not this one

[snicoll]

Thanks for the feedback. Timeout for control queries, I see.

This is worth exposing I guess although it's not immediately obvious from the exception you've shared that advanced.control-connection.timeout is configuring this. Paging @adutra in case there's something else we should know.

[smakalias]

I solved this issue by setting
advanced.control-connection.timeout
by setting manually at Datastax Driver Option this property was not exposed at spring boot side.

Hi @logicatmidod , I'm facing the same issue when running migrations (we use https://github.com/patka/cassandra-migration) - the issue is really weird, it seems to occur randomly in PRD installations (either low-data-load or heavy-data-load) and I cannot replicate locally).

Could you please elaborate how did you actually set the advanced.control-connection.timeout value so I can rule out things?
Also, is there a clear way to know if this value is picked up or Spring Boot overrides it?

Thanks in advance for your response and help

[snicoll]

@smakalias this is described in the documentation, something like:

@Bean
DriverConfigLoaderBuilderCustomizer cassandraDriverCustomizer() {
    return (builder) -> builder.withDuration(
        DefaultDriverOption.CONTROL_CONNECTION_TIMEOUT, Duration.ofSeconds(10));
}

Spring Boot is not going to override anything you've specified yourself. You can also inject the DriverConfigLoader and look at its config. Going forward please ask questions on StackOverflow, as mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements.