yes, of course. Private ip is real ip address of node. Cassandra can listen on this ip only. elastic ip is external. It belongs to AWS firewall. It is similar to your web router. You can forward your external port to local one, but application running on your local node doesn't know anything about it.
On Wed, Jun 25, 2014 at 1:25 PM, Huiliang Zhang <zhl...@gmail.com> wrote: > Thanks. In fact, it is Cassandra that returns private ip of nodes to my > program by: > > client.describe_ring(keyspace) > > Then the program will start communicate with Cassandra through the private > ips. One way is to translate the ips myself. > > > On Tue, Jun 24, 2014 at 10:40 PM, Andrey Ilinykh <ailin...@gmail.com> > wrote: > >> you can set rpc_address to 0.0.0.0, then it will listen on all >> interfaces. Also you have to modify security group settings to allow >> incoming connection for port 9160. But it is a really bad idea. By this >> way you open your cluster to whole world, ssh tunnel is the best way. >> >> >> On Tue, Jun 24, 2014 at 10:01 PM, Huiliang Zhang <zhl...@gmail.com> >> wrote: >> >>> Thanks. Is there a way to configure Cassandra to use elastic ip instead >>> of private ip? >>> >>> >>> On Tue, Jun 24, 2014 at 9:29 PM, Andrey Ilinykh <ailin...@gmail.com> >>> wrote: >>> >>>> Cassandra knows nothing about elastic ip. You have to use ssh tunnel or >>>> run your client on ec2 instance. >>>> >>>> Thank you, >>>> Andrey >>>> >>>> >>>> On Tue, Jun 24, 2014 at 8:55 PM, Huiliang Zhang <zhl...@gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I am using Cassandra on EC2 instances. My cassandra always returns >>>>> private ips of the instances to the thrift program. Then the program >>>>> cannot >>>>> connect to the private ips. >>>>> >>>>> I already changed the >>>>> rpc_address: elastic ip >>>>> rpc_address: elastic ip >>>>> >>>>> Then I restarted the cassandra cluster. But the system.peers still >>>>> save the private ips as peer address. >>>>> >>>>> How to fix this? >>>>> >>>>> Thanks, >>>>> Huiliang >>>>> >>>>> >>>> >>> >> >
