Problems with cassandra on AWS

2016-07-10 Thread Kant Kodali
Hi Guys,

I installed a 3 node Cassandra cluster on AWS and my replication factor is
3. I am trying to insert some data into a table. I set the consistency
level of QUORUM at a Cassandra Session level. It only inserts into one node
and unable to talk to other nodes because it is trying to contact other
nodes through private IP and obviously that is failing so I am not sure how
to change settings in say cassandra.yaml or somewhere such that rpc_address
in system.peers table is updated to public IP's? I tried changing the seeds
to all public IP's that didn't work as it looks like ec2 instances cannot
talk to each other using public IP's. any help would be appreciated!

Thanks,
kant


Re: Problems with cassandra on AWS

2016-07-10 Thread daemeon reiydelle
xWell, I seem to recall that the private IP's are valid for communications
WITHIN one VPC. I assume you can log into one machine and ping (or ssh) the
others. If so, check that cassandra.yaml is not set to listen on 127.0.0.1
(localhost).


*...*



*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198
<%28%2B1%29%20415.501.0198>London (+44) (0) 20 8144 9872
<%28%2B44%29%20%280%29%2020%208144%209872>*

On Sun, Jul 10, 2016 at 4:54 PM, Kant Kodali  wrote:

> Hi Guys,
>
> I installed a 3 node Cassandra cluster on AWS and my replication factor is
> 3. I am trying to insert some data into a table. I set the consistency
> level of QUORUM at a Cassandra Session level. It only inserts into one node
> and unable to talk to other nodes because it is trying to contact other
> nodes through private IP and obviously that is failing so I am not sure how
> to change settings in say cassandra.yaml or somewhere such that rpc_address
> in system.peers table is updated to public IP's? I tried changing the seeds
> to all public IP's that didn't work as it looks like ec2 instances cannot
> talk to each other using public IP's. any help would be appreciated!
>
> Thanks,
> kant
>