This failure is from hasRecreateSchemaActionSet:
Could not reach any contact point, make sure you've provided valid addresses (showing first 1, use getErrors() for more: Node(endPoint=/172.17.0.1:32832, hostId=null, hashCode=401ca295): com.datastax.oss.driver.api.core.DriverTimeoutException: [s0|control|id: 0x97060aa4, L:/172.17.0.1:54734 - R:/172.17.0.1:32832] init query OPTIONS: timed out after 500 ms)
It looks like we could do with increasing a timeout somewhere. 500ms doesn't appear to be enough time for a response to be received reliably.
Comment From: snicoll
@mbhave I don't understand the proposed change as advanced.connection.init-query-timeout is already mapped from the connection-timeout property. It looks like changing the already existing property should do it.
Comment From: snicoll
I've validated a value without unit is mapped to ms. The previous timeout was 10s. However, this test is creating a keyspace upfront and that change of yours make sure that operation uses the 1s timeout. I've now adapted the test to apply timeouts on both operations. I wish I could reuse the same config but unfortunately, the keyspace creation has to be created before the CqlSession initializes itself so creating a session without the keyspace seems the only solution.
Comment From: snicoll
I discussed this a bit more with @mbhave and we concluded that that change wasn't ideal either. That discussion led to another proposal where we create the CqlSession ourselves, intializing the keyspace if necessary.
This also covers more ground for that particular integration test, see b6c5c3a
Comment From: adutra
Just a heads up that since driver 4.8.0, the timeout for init queries was raised to 5 seconds, see JAVA-2841. This should hopefully make integration tests much more reliable.
Comment From: snicoll
Thanks for the heads up @adutra.