Re: Service discovery in the Cassandra cluster

You’re free to supply your own Seed Provider. The Seed provider that comes with cassandra needs hard coded IPs, but there’s no reason why it has to be that way. There’s a handful of ideas here: https://issues.apache.org/jira/browse/CASSANDRA-12627

Re: Service discovery in the Cassandra cluster

Service discovery (aka "note some IPs") should be part of the cluster bootstrapping and management. See for example how elastic is doing this. Or consul. Its pretty standard practice these days. -- Roman On Tue, May 2, 2017 at 5:08 PM Steve Robenalt wrote: > Hi Roman, > > I'm assuming you were

Re: Service discovery in the Cassandra cluster

My compliments to all of you for being adults, excessively kind, and definitely excessively nice. *...* *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872* On Tue, May 2, 2017 at 5:08 PM, Steve Robenalt wrote: > Hi Roman, > > I'm assuming you were intending your f

Re: Service discovery in the Cassandra cluster

Hi Roman, I'm assuming you were intending your first statement to be in jest, but it's really not that hard to startup a Cassandra cluster. The defaults are pretty usable, so if all you want to do is set the IPs and start it up, the cluster probably will just take care of everything else. So I je

Re: Service discovery in the Cassandra cluster

Lol yeah, why I guess I run some ec2 instances, drop some cassandra deb packages on 'em - the thing will figure out how to run... Also, how would you get "initial state of the cluster" if the cluster... is being initialized? Or that's easy, according to the docs - just hardcode some seed IPs into

Re: Service discovery in the Cassandra cluster

Why do you have to figure out what’s up w/ them by accident? You’ve gotten all the information you need. Seeds are used to get the initial state of the cluster and as an optimization to spread gossip faster. That’s it. > On May 1, 2017, at 4:37 PM, Roman Naumenko wrote: > > Well, I gues

Re: Service discovery in the Cassandra cluster

Well, I guess I have to figure out what’s up with IPs/hostnames by experiment. Information about service discovery is practically absent. Not to mention all important details about fqdns/hostnames, automatic replacing seed nodes or what not. — Roman > On May 1, 2017, at 4:14 PM, Jon Haddad wro

Re: Service discovery in the Cassandra cluster

The in-tree docs do not mention this anywhere, and even have some of the answers you’re asking: https://cassandra.apache.org/doc/latest/faq/index.html?highlight=seed#what-are-seeds The DataStax docs are main

Re: Service discovery in the Cassandra cluster

The docs mention IP addresses everywhere. http://docs.datastax.com/en/archived/cassandra/2.0/cassandra/operations/ops_replace_seed_node.html Promote an existing node to a seed node by adding its

Re: Service discovery in the Cassandra cluster

Yes, you can use host names. That merely adds another level of configuration. When using terraform, I often use node names like and just use those. They are only routable within the region/VPC but are in fact already in dns. You do have to watch out as if you change the seeds (in tf) or the cluste

Re: Service discovery in the Cassandra cluster

Sure, you could use DNS. Where does it say IP addresses are a requirement? > On May 1, 2017, at 1:36 PM, Roman Naumenko wrote: > > If I understand how Cassandra nodes work, they must contain a list of seed’s > IP addressed in config file. > > This requirement makes cluster setup unnecessarily

Service discovery in the Cassandra cluster

If I understand how Cassandra nodes work, they must contain a list of seed’s IP addressed in config file. This requirement makes cluster setup unnecessarily complicated. Is it possible to use DNS name for seed nodes? Thanks, — Roman -