Was this page helpful?
ScyllaDB Java Driver is available under the Apache v2 License. ScyllaDB Java Driver is a fork of DataStax Java Driver. See Copyright here.
Connectivity¶
Quick overview¶
How the driver reaches the nodes of a cluster, and what each kind of network needs configured.
contact points and a local datacenter, and nothing else, when every node is reachable at the address it broadcasts – VPC peering, AWS Transit Gateway, or a direct connection over the public internet.
advanced.client-routeswhen the cluster sits behind a cloud private endpoint that publishes a per-node endpoint mapping.advanced.address-translatorfor anything else, see address resolution.
A CqlSession starts from the contact points you give it, discovers the rest of the cluster from
system.peers, and then opens connections to each node at the address that node broadcasts. Whether
that last step works is a property of your network, not of the driver, and it is what the pages in
this section are about.
How your application reaches the cluster |
What the driver needs |
|---|---|
VPC peering, Transit Gateway or a direct connection – every node is reachable at the address it broadcasts |
contact points and a local datacenter, nothing else |
A cloud private endpoint that publishes a per-node entry in |
|
A proxy in front of the cluster – one hostname for every node (a single-endpoint PrivateLink included), one per subnet, or EC2 multi-region |
an address translator |
A cloud private endpoint appears in two of those rows, and the difference is what the cluster
publishes: a per-node endpoint mapping the driver can read means client routes, while one hostname
standing in front of every node means an address translator. The translator has to give each node
its own address and port: nodes translated to the same one share a single endpoint, so the proxy
rather than the driver picks the node, and token-aware and shard-aware routing stop working.
FixedHostNameAddressTranslator keeps each node’s port, which on ScyllaDB is the same for every
node, so it does not meet this on its own. SubnetAddressTranslator has the same limit within each
datacenter, since it maps a whole subnet to one proxy address.
Two things are the same in every case and are covered elsewhere: SSL for encrypting the traffic, and authentication for proving who you are. Contact points themselves – including what happens when you give one as a hostname that resolves to several addresses – are covered under address resolution.