[FLINK-28198][connectors][cassandra] raise driver timeouts per session request and raise it higher than cluster side timetouts

[echauchot]

Contribution Checklist

What is the purpose of the change

Raise driver timeouts per session request and raise it higher than cluster side timetouts

Brief change log

Change in the CassandraITCase

Verifying this change

This change is already covered by existing tests, such as CassandraITCase

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

R: @MartijnVisser

[flinkbot]

CI report:

• a7855f4 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[zentol]

Isn't this already set in the cluster builder?

[echauchot]

Yes but as I wrote in the ticket:

"the driver timeouts were set on the clusterBuilder because previous timeout errors were only on test cases. Here, the request timeouts are on session.execute that do not use the ClusterBuilder. Thus, they use the default 12s timeout. I'll raise to 36s per session request."

the ClusterBuilder is only used for Sinks, InputFormats, OutputFormats, etc... but not for session.execute requests

[echauchot]

@zentol there has been several of these timeout issues that make the build flaky. @MartijnVisser pinged me to quickly solve this issue. Tell me if you need anything more on this PR.

[echauchot]

@flinkbot run azure

[echauchot]

@flinkbot run azure

[MartijnVisser]

@echauchot Thanks for the PR. Let's get this merged :)