Re: Problems with cassandra on AWS

[Alain RODRIGUEZ]

Hi Kant.

it looks like ec2 instances cannot talk to each other using public IP's


"talk to each other" --> port 7000 (if not using ssl, 7001 if using it).
Make sure this port is open. From IP_1: telnet ip_2 7000 will tell you if
the port is opened.

"using public IP's" --> Are you using Ec2Snitch or Ec2MultiRegionSnitch.
The former uses exclusively private IP (listen_address, rpc_address and
broadcast_address empty / commented). The latter uses public ip for
broadcast_address. You need then to make sure ports are open between the
private IPs.

Having a look at 'nodetool status' before running operations should help
you determine the current status for your cluster. Nodes should be showing
UN status (Up, Normal).

C*heers,
---
Alain Rodriguez - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-07-11 10:02 GMT+02:00 Riccardo Ferrari :

> I would check your security group settings, you need to allow
> communication on cassandra ports (ie 9042,...)
>
> On Mon, Jul 11, 2016 at 8:17 AM, daemeon reiydelle 
> wrote:
>
>> 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
>>>
>>
>>
>

Re: Problems with cassandra on AWS

[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
>

Problems with cassandra on AWS

[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