From my understanding, the main thing to be aware of is that Cassandra’s default SeedProvider doesn't resolve multiple A records, so you’re actually limited in terms of the load balancing/DNS configurations you can use.
You can however write alternative seed providers which have different (perhaps more appropriate) behaviour, see here <https://github.com/k8ssandra/management-api-for-apache-cassandra/blob/a317ba40fae8e2b11eecde01ad5e6ee15aebdb0f/management-api-agent-4.x/src/main/java/org/apache/cassandra/locator/K8SeedProvider4x.java> for an example. > On 23 Jun 2022, at 10:53 pm, Durity, Sean R <sean_r_dur...@homedepot.com> > wrote: > > It can work to use host names. We have done it for temporary clusters where > there is at least a theoretical possibility of an ip address change. I don't > know all the trade-offs of using host names, since we don't do that for > production. > > > Sean R. Durity > > > INTERNAL USE > > -----Original Message----- > From: Marc Hoppins <marc.hopp...@eset.com> > Sent: Thursday, June 23, 2022 3:33 AM > To: user@cassandra.apache.org > Subject: [EXTERNAL] Seed List > > Hi guys, > > Documentation (for almost everything) uses IP addresses for seeds, is it > possible to use the FQDN instead for the seeds (cass.yaml)? It is far easier > to read/use names. > > Thanks > > M
