Re: Securing a Cassandra 2.2.6 Cluster

2016-10-31 Thread Vladimir Yudovin
I would set rpc_address to 0.0.0.0 and broadcast_rpc_address to EACH_IP This allows to connect to both 127.0.0.1 from inside and to IP from outside. By a way, I see that port 7000 bound to external IP. Aren't both node in the same network? If yes, use internal IPs. Best regards, Vladimi

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-31 Thread Vladimir Yudovin
>Both nodes can be seeds. Probably I misunderstood Raimund as setting each node as the only seed. If he set both IP on both nodes it's OK. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Sun, 30 Oct 2016 14:48:00 -0400Jonathan H

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Jonathan Haddad
I'm not sure why you aren't able to connect with cqlsh, there may be something in your log files to help figure that out. As for your config, even if you do figure out why you can't connect, you're still going to have to change your settings since you won't be able to connect to your cluster from

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Raimund Klein
Hi guys, Thank you for your responses. Let me try to address them: - I just tried cqlsh directly with the IP, no change in behaviour. (I previously tried the hostnames, didn't work either.) - As for the "empty" ..._address: I meant that I leave these blank. Please let me quote from t

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Jonathan Haddad
I always prefer to set the listen interface instead of listen adress Both nodes can be seeds. In fact, there should be more than one seed. Having your first 2 nodes as seeds is usual the correct thing to do. On Sun, Oct 30, 2016 at 8:28 AM Vladimir Yudovin wrote: > >Empty listen_address and rpc_

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Vladimir Yudovin
>Empty listen_address and rpc_address. What do you mean by "Empty"? You should set either ***_address or ***_interface. Otherwise Cassandra will not listen on port 9042. >Open ports 9042, 7000 and 7001 for external communication. Only port 9042 should be open to the world, Port 7000 for int

Re: Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Jonathan Haddad
Dis you try the external IP with cqlsh? On Sun, Oct 30, 2016 at 8:12 AM Raimund Klein wrote: > Hi everyone, > > We've managed to set up a Cassandra 2.2.6 cluster of two physical nodes > (nodetool sees both of them, so I'm quite certain the cluster is indeed > active). My steps to create the clust

Securing a Cassandra 2.2.6 Cluster

2016-10-30 Thread Raimund Klein
Hi everyone, We've managed to set up a Cassandra 2.2.6 cluster of two physical nodes (nodetool sees both of them, so I'm quite certain the cluster is indeed active). My steps to create the cluster were (this applies to both machines): - Empty listen_address and rpc_address. - Define a cluster_n