Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document how to fix the driver/jvm to be able to survive a cassandra … #963

Merged
merged 1 commit into from
Jul 11, 2022
Merged

Document how to fix the driver/jvm to be able to survive a cassandra … #963

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/src/main/paradox/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,13 @@ One important setting is to configure the database driver to retry the initial c

It is not enabled automatically as it is in the driver's reference.conf and is not overridable in a profile.

If the ip addresses of your cassandra nodes might change (e.g. if you use k8s) then

`datastax-java-driver.advanced.resolve-contact-points = false`

should also be set (resolves a dns address again when new connections are created). This also implies disabling java's dns cache with `-Dnetworkaddress.cache.ttl=0`.


### Cassandra driver overrides

@@snip [reference.conf](/core/src/main/resources/reference.conf) { #profile }
Expand Down