You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Todd Nine <to...@gmail.com> on 2012/03/08 20:41:58 UTC
Multic DC on EC2 with no VPC
Hi all,
I've recently upgraded a test cluster from 0.8.x to 1.0.8 for testing multi data center communications. I have the following configuration file on 3 nodes in a single data center.
https://gist.github.com/4671e4ae562a47f96ed2
However, when I run node tool on any of these nodes, they recognize the others are up, but no data is available.
nodetool -h localhost ring
Address DC Rack Status State Load Owns Token
113427455640312821154458202477256070485
10.172.106.192 UNKNOWN-DC UNKNOWN-RACKDown Normal ? 33.33% 0
50.18.3.222 us-west 1c Up Normal 3.95 GB 33.33% 56713727820156410577229101238628035242
10.172.134.239 UNKNOWN-DC UNKNOWN-RACKDown Normal ? 33.33% 113427455640312821154458202477256070485
If I remove the broadcast_address from the yaml, everything works fine, but I can't communicate across data centers. Any ideas why I'm getting this error? The listen_address is the private ip, and the broadcast_address is the public ip.
Thanks,
Todd
Re: Multic DC on EC2 with no VPC
Posted by Vijay <vi...@gmail.com>.
Can you check if the ports are open and you are able to communicate?
UNKNOWN-DC is printed when it is not gossiping with the other node.
I would check the security group settings and verify if the telnet to the
targe port is working as expected.
Regards,
</VJ>
On Thu, Mar 8, 2012 at 11:41 AM, Todd Nine <to...@gmail.com> wrote:
> Hi all,
> I've recently upgraded a test cluster from 0.8.x to 1.0.8 for testing
> multi data center communications. I have the following configuration file
> on 3 nodes in a single data center.
>
> https://gist.github.com/4671e4ae562a47f96ed2
>
> However, when I run node tool on any of these nodes, they recognize the
> others are up, but no data is available.
>
>
> nodetool -h localhost ring
> Address DC Rack Status State Load
> Owns Token
>
> 113427455640312821154458202477256070485
> 10.172.106.192 UNKNOWN-DC UNKNOWN-RACKDown Normal ?
> 33.33% 0
> 50.18.3.222 us-west 1c Up Normal 3.95 GB
> 33.33% 56713727820156410577229101238628035242
> 10.172.134.239 UNKNOWN-DC UNKNOWN-RACKDown Normal ?
> 33.33% 113427455640312821154458202477256070485
>
> If I remove the broadcast_address from the yaml, everything works fine,
> but I can't communicate across data centers. Any ideas why I'm getting
> this error? The listen_address is the private ip, and the
> broadcast_address is the public ip.
>
> Thanks,
> Todd
>
Re: Multic DC on EC2 with no VPC
Posted by aaron morton <aa...@thelastpickle.com>.
I wonder why the nodes are not in a known DC ? Are you using the property file snitch or EC2 snitch ? If the DC cannot be identified the NTS will not be able to find enough nodes to meet the CL.
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 9/03/2012, at 8:41 AM, Todd Nine wrote:
> Hi all,
> I've recently upgraded a test cluster from 0.8.x to 1.0.8 for testing multi data center communications. I have the following configuration file on 3 nodes in a single data center.
>
> https://gist.github.com/4671e4ae562a47f96ed2
>
> However, when I run node tool on any of these nodes, they recognize the others are up, but no data is available.
>
>
> nodetool -h localhost ring
> Address DC Rack Status State Load Owns Token
> 113427455640312821154458202477256070485
> 10.172.106.192 UNKNOWN-DC UNKNOWN-RACKDown Normal ? 33.33% 0
> 50.18.3.222 us-west 1c Up Normal 3.95 GB 33.33% 56713727820156410577229101238628035242
> 10.172.134.239 UNKNOWN-DC UNKNOWN-RACKDown Normal ? 33.33% 113427455640312821154458202477256070485
>
> If I remove the broadcast_address from the yaml, everything works fine, but I can't communicate across data centers. Any ideas why I'm getting this error? The listen_address is the private ip, and the broadcast_address is the public ip.
>
> Thanks,
> Todd