> On Thu, Feb 24, 2011 at 4:04 AM, Himanshi Sharma <*
>>> himanshi.sha...@tcs.com* > wrote:
>>> giving private ip to rpc address gives the same exception
>>> and the keeping it blank and providing public to listen also fails. I
>>> tried keeping both blank
cpdump it gives
>>
>> [root@ip-10-136-75-201 ~]# tcpdump -i 50.18.60.117 -n port 7000
>> tcpdump: Invalid adapter index
>>
>> Not able to figure out wats this ??
>>
>> Thanks,
>> Himanshi
>>
>>
>>
>
4.72.22.87...
> Connected to 184.72.22.87.
> Escape character is '^]'.
>
>
>
> -Dave Viner wrote: -
> To: *user@cassandra.apache.org*
> From: Dave Viner <*davevi...@gmail.com* >
> Date: 02/24/2011 11:59AM
> cc: Himanshi Sharma <*himanshi.sha..
Date:
02/24/2011 04:27 PM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
Himanshi,
you could try adding your public IP address to an internal interface and
DNAT the packets to it. This shouldn't give you any problems with your
normal traffic. Tell Cassand
-Dave Viner wrote: -
>
> To: user@cassandra.apache.org
> From: Dave Viner
> Date: 02/24/2011 11:59AM
> cc: Himanshi Sharma
>
> Subject: Re: Cassandra nodes on EC2 in two different regions not
> communicating
>
> Try using the private ipv4 address in the rpc_addres
7;nt show the node in another region.
Thanks,
Himanshi -Dave Viner wrote: -
To: user@cassandra.apache.org From: Dave Viner < davevi...@gmail.com > Date: 02/24/2011 10:43AM
Subject: Re: Cassandra nodes on EC2 in two different regions not communicating That looks like it's n
@cassandra.apache.org
> From: Dave Viner
> Date: 02/24/2011 10:43AM
>
> Subject: Re: Cassandra nodes on EC2 in two different regions not
> communicating
>
> That looks like it's not an issue of communicating between nodes. It
> appears that the node can not bind to th
user@cassandra.apache.org
Date:
02/23/2011 11:01 PM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
internal EC2 ips (10.xxx.xxx.xxx) work across availability zones (e.g., from us-east-1a to us-east-1b) but do not work across regions (e.g., us-east to us-we
e again its own
> elastic ip
>
> listen_address: 175.41.143.192
> rpc_address: 175.41.143.192
>
> Thanks,
> Himanshi
>
>
>
>
>
> From:
> Dave Viner
> To: user@cassandra.apache.org Date: 02/23/2011 11:01 PM Subject: Re:
> Cassandra nodes on EC2 in two diff
: 175.41.143.192
rpc_address: 175.41.143.192
Thanks,
Himanshi
From:
Dave Viner
To:
user@cassandra.apache.org
Date:
02/23/2011 11:01 PM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
internal EC2 ips (10.xxx.xxx.xxx) work across availability zones (e.g.,
from us-east
he nodes through public ips.
From:
Dave Viner
To:
user@cassandra.apache.org
Date:
02/23/2011 11:01 PM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
internal EC2 ips (10.xxx.xxx.xxx) work across availability zones (e.g.,
from us-east-1a to us-east-1b) but do
shi.sha...@tcs.com> wrote:
>
> Ya they do. Have specified Public DNS in seed field of each node in
> Cassandra.yaml...nt able to figure out what the problem is ???
>
> From: Sasha Dolgy <[4]sdo.
; > wrote:
>>
>>>
>>> Ya they do. Have specified Public DNS in seed field of each node in
>>> Cassandra.yaml...nt able to figure out what the problem is ???
>>>
>>>
>>>
>>>
>>
>
>>
>> Ya they do. Have specified Public DNS in seed field of each node in
>> Cassandra.yaml...nt able to figure out what the problem is ???
>>
>>
>>
>>
>> From: Sasha Dolgy To: user@cassandra.apache.org Date:
>> 02/23/2011
&
Public DNS in seed field of each node in
> Cassandra.yaml...nt able to figure out what the problem is ???
>
>
>
>
> From: Sasha Dolgy To: user@cassandra.apache.org Date:
> 02/23/2011
> 02:56 PM Subject: Re: Cassandra nodes on EC2 in two differe
Ya they do. Have specified Public DNS in seed field of each node in
Cassandra.yaml...nt able to figure out what the problem is ???
From:
Sasha Dolgy
To:
user@cassandra.apache.org
Date:
02/23/2011 02:56 PM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
did
ma Date: 02/23/2011 11:36 AM Subject: Re:
> Cassandra nodes on EC2 in two different regions not communicating
> --
>
>
>
> If you login to one of the nodes, can you telnet to port 7000 on the other
> node?
>
> If not, then almost certainly it&#x
:
user@cassandra.apache.org
Cc:
Himanshi Sharma
Date:
02/23/2011 11:36 AM
Subject:
Re: Cassandra nodes on EC2 in two different regions not communicating
If you login to one of the nodes, can you telnet to port 7000 on the other
node?
If not, then almost certainly it's a firewall/Security
If you login to one of the nodes, can you telnet to port 7000 on the other
node?
If not, then almost certainly it's a firewall/Security Group issue.
You can find out the security groups for any node by logging in, and then
running:
% curl "http://169.254.169.254/latest/meta-data/security-groups"
19 matches
Mail list logo
