You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Adil <ad...@gmail.com> on 2014/11/13 19:26:34 UTC
Cassandra communication between 2 datacenter
Hi,
we have two datacenter with those inof:
Cassandra version 2.1.0
DC1 with 5 nodes
DC2 with 5 nodes
we set the snitch to GossipingPropertyFileSnitch and in
cassandra-rackdc.properties we put:
in DC1:
dc=DC1
rack=RAC1
in DC2:
dc=DC2
rack=RAC1
and in every node's cassandra.yaml we define two seeds of DC1 and two seed
of DC2.
we restart both DC, we create un keyspace with NetworkTopologyStrategy in
DC1 and we suspect that will be created also in DC2 but it's not the
case...so we create the same keyspace in DC2, we create a table in both DC,
we did un insert in DC1 but doing un select from the same table in DC2 we
found 0 rows.
so it seems that our clusters are not communicating between them.
doing a nodetool status overs each DC we see only the 5 nodes corresponding
to the current DC.
are we missed some configuration?
thanks in advance.
Re: Cassandra communication between 2 datacenter
Posted by Adil <ad...@gmail.com>.
Thank you Eric, the problem in fact was that the ports were open only in
one sense.
now is working.
2014-11-13 22:38 GMT+01:00 Eric Plowe <er...@gmail.com>:
> Are you sure that both DC's can communicate with each other over the
> necessary ports?
>
> On Thu, Nov 13, 2014 at 3:46 PM, Adil <ad...@gmail.com> wrote:
>
>> yeh we started nodes one at time....my doubt is if we should configure
>> alse cassandra-topology.properties or not? we leave it with default vlaues
>>
>> 2014-11-13 21:05 GMT+01:00 Robert Coli <rc...@eventbrite.com>:
>>
>>> On Thu, Nov 13, 2014 at 10:26 AM, Adil <ad...@gmail.com> wrote:
>>>
>>>> Hi,
>>>> we have two datacenter with those inof:
>>>>
>>>> Cassandra version 2.1.0
>>>> DC1 with 5 nodes
>>>> DC2 with 5 nodes
>>>>
>>>> we set the snitch to GossipingPropertyFileSnitch and in
>>>> cassandra-rackdc.properties we put:
>>>> in DC1:
>>>> dc=DC1
>>>> rack=RAC1
>>>>
>>>> in DC2:
>>>> dc=DC2
>>>> rack=RAC1
>>>>
>>>> and in every node's cassandra.yaml we define two seeds of DC1 and two
>>>> seed of DC2.
>>>>
>>>
>>> Do you start the nodes one at a time, and then consult nodetool ring
>>> (etc.) to see if the cluster coalesces in the way you expect?
>>>
>>> If so, a Keyspace created in one should very quickly be created in the
>>> other.
>>>
>>> =Rob
>>> http://twitter.com/rcolidba
>>>
>>
>>
>
Re: Cassandra communication between 2 datacenter
Posted by Eric Plowe <er...@gmail.com>.
Are you sure that both DC's can communicate with each other over the
necessary ports?
On Thu, Nov 13, 2014 at 3:46 PM, Adil <ad...@gmail.com> wrote:
> yeh we started nodes one at time....my doubt is if we should configure
> alse cassandra-topology.properties or not? we leave it with default vlaues
>
> 2014-11-13 21:05 GMT+01:00 Robert Coli <rc...@eventbrite.com>:
>
>> On Thu, Nov 13, 2014 at 10:26 AM, Adil <ad...@gmail.com> wrote:
>>
>>> Hi,
>>> we have two datacenter with those inof:
>>>
>>> Cassandra version 2.1.0
>>> DC1 with 5 nodes
>>> DC2 with 5 nodes
>>>
>>> we set the snitch to GossipingPropertyFileSnitch and in
>>> cassandra-rackdc.properties we put:
>>> in DC1:
>>> dc=DC1
>>> rack=RAC1
>>>
>>> in DC2:
>>> dc=DC2
>>> rack=RAC1
>>>
>>> and in every node's cassandra.yaml we define two seeds of DC1 and two
>>> seed of DC2.
>>>
>>
>> Do you start the nodes one at a time, and then consult nodetool ring
>> (etc.) to see if the cluster coalesces in the way you expect?
>>
>> If so, a Keyspace created in one should very quickly be created in the
>> other.
>>
>> =Rob
>> http://twitter.com/rcolidba
>>
>
>
Re: Cassandra communication between 2 datacenter
Posted by Adil <ad...@gmail.com>.
yeh we started nodes one at time....my doubt is if we should configure alse
cassandra-topology.properties or not? we leave it with default vlaues
2014-11-13 21:05 GMT+01:00 Robert Coli <rc...@eventbrite.com>:
> On Thu, Nov 13, 2014 at 10:26 AM, Adil <ad...@gmail.com> wrote:
>
>> Hi,
>> we have two datacenter with those inof:
>>
>> Cassandra version 2.1.0
>> DC1 with 5 nodes
>> DC2 with 5 nodes
>>
>> we set the snitch to GossipingPropertyFileSnitch and in
>> cassandra-rackdc.properties we put:
>> in DC1:
>> dc=DC1
>> rack=RAC1
>>
>> in DC2:
>> dc=DC2
>> rack=RAC1
>>
>> and in every node's cassandra.yaml we define two seeds of DC1 and two
>> seed of DC2.
>>
>
> Do you start the nodes one at a time, and then consult nodetool ring
> (etc.) to see if the cluster coalesces in the way you expect?
>
> If so, a Keyspace created in one should very quickly be created in the
> other.
>
> =Rob
> http://twitter.com/rcolidba
>
Re: Cassandra communication between 2 datacenter
Posted by Robert Coli <rc...@eventbrite.com>.
On Thu, Nov 13, 2014 at 10:26 AM, Adil <ad...@gmail.com> wrote:
> Hi,
> we have two datacenter with those inof:
>
> Cassandra version 2.1.0
> DC1 with 5 nodes
> DC2 with 5 nodes
>
> we set the snitch to GossipingPropertyFileSnitch and in
> cassandra-rackdc.properties we put:
> in DC1:
> dc=DC1
> rack=RAC1
>
> in DC2:
> dc=DC2
> rack=RAC1
>
> and in every node's cassandra.yaml we define two seeds of DC1 and two seed
> of DC2.
>
Do you start the nodes one at a time, and then consult nodetool ring (etc.)
to see if the cluster coalesces in the way you expect?
If so, a Keyspace created in one should very quickly be created in the
other.
=Rob
http://twitter.com/rcolidba