Personally I wouldn't bother with a VPN. You can limit access to a group
of servers easily via security groups and not have a single point of
failure. I wrote a utility to manage this. If you're bringing up a new
VPC + Cassandra servers every day, you can trivially apply a set of rules
to your V
Rather than using public IPs on the Cassandra nodes at all I would set up a
VPN.
1. Make sure all Cassandra nodes are on the same private network with
static IPs
2. Set up a new micro instance with a static public IP, make sure it has a
static IP on the private network as well
3. Install OpenVPN o
Basically your client just needs a route to talk to the IP being broadcast
by each node. We do plenty in EC2 and we use the instance private IP in
the broadcast address. If you are doing multi-datacenter in EC2 it gets a
little harrier, where you need to use the public IP (but not necessarily
ela
You've been talking about configuring static, public IPs. Public IPs are
only needed if you want to connect to your Cassandra servers from a public
network aka not from the same datacenter.
AWS instances don't get a new IP on rebooting. The instance doesn't
shutdown when you tell a server to reb
Jonathan, I have some difficulties in understanding what you're talking
about. A client is a program connecting to a cassandra instance. All it
needs to know is an IP, a keyspace and a table to operate. My client is
nothing more than a simple textual version of a program like datastax
devcenter
If your client is in the same DC, then you shouldn't use *public* ip
addresses. If you're using a recent version of Cassandra you can just set
the listen_interface and rpc_interface to whatever network interface you've
got.
If you're really changing IPs when you reboot machines (I have no idea wh
Yes, the client uses the same datacenter (us-west-2).
Maybe I haven't explained well the situation. I'm not asking to connect
to nodes *without* using a static IP address, but allowing Cassandra to
determine the current public address at the time of connection.
Spark, for example, uses shell scr
So you're not running the client in the same DC as your Cassandra cluster.
In that case you'll need to be able to connect to the public address of all
the nodes. Technically you could have a whitelist and only connect to 1, I
wouldn't recommend it.
This is no different than any other database in
Seems to be not the case when connecting to my (single) data center
using the java connector with a small client I have developed for testing.
For the broadcast_rpc_address I have configured the local IP of the
nodes. The cluster works fine and nodes communicates fairly well using
their local IP
Public IP? No, not required unless you're running multiple DCs.
Where are you running a DC that IPs aren't cheap? If you're in AWS they're
basically free (or at least the cheapest section of your bill by far)
On Sun, Oct 4, 2015 at 5:59 PM Renato Perini
wrote:
> Is cassandra really supposed
Is cassandra really supposed to have a static public IP for each and
single node in the cluster?
This seems to be expensive (static IPs are nor free neither cheap),
still the broadcast_rpc_address expects a static IP for client
communications (load balancing, contact points, etc.)
Is there some
11 matches
Mail list logo
