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

Re: Cassandra communication between 2 datacenter

yeh we started nodes one at timemy 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 adil.cha...@gmail.com wrote: Hi, we have two

Re: Cassandra communication between 2 datacenter

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 eric.pl...@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 adil.cha

Cassandra default consistency level on multi datacenter

Hi, We are using two datacenter and we want to set the default consistency level to LOCAL_ONE instead of ONE but we don't know how to configure it. We set LOCAL_QUORUM via cql driver for the desired queries but we won't do the same for the default one. Thanks in advance Adil

Re: Cassandra default consistency level on multi datacenter

yes, already found...via the QueryOptions 2014-11-15 1:28 GMT+01:00 Tyler Hobbs ty...@datastax.com: Cassandra itself does not have default consistency levels. These are only configured in the driver. On Fri, Nov 14, 2014 at 8:54 AM, Adil adil.cha...@gmail.com wrote: Hi, We are using two

logging over multi-datacenter

QUORUM consistency level (2 data-center). my question is if the java driver cql uses the same condition and if there is a way to set the consistency level to like LOCAL_ONE. Thanks Adil

Re: logging over multi-datacenter

cassandra version 2.1.2 with the default user we create another user and with this one we could login even if only one node is up 2014-11-20 15:16 GMT+01:00 Mark Reddy mark.l.re...@gmail.com: Hi Adil, What Cassandra version are you using? Are you using the default user or a non-default user

Re: logging over multi-datacenter

ok thank you. 2014-11-20 16:02 GMT+01:00 Mark Reddy mark.l.re...@gmail.com: Hi Adil, When using the default superuser ('cassandra') a consistency level of QUORUM is used. When using other users ONE is used. You are not supposed to use 'cassandra' user directly, except to create another

Re: Mutable primary key in a table

Hi, it seems you are doing some thing wrong in your model, why can you go with updating columns of key1 instead of deleting/inserting row key? 2015-02-06 15:02 GMT+01:00 Ajaya Agrawal ajku@gmail.com: Hi guys, I want to take a row with primary key K1, rewrite it with primary key K2, and

nodetool repair

Hi guys, We have two DC, we are planning to schedule running nodetool repair weekly, my question is : nodetool repair is cross cluster or not? it's sufficient to run it without options on a node or should be scheduled on every node with the host option. Thanks

electricity outage problem

the same node in DC as own, we have noticed this message in the log "received an invalid gossip generation for peer", does anyone know how to resolve this problem? should we purge the gossip? thanks Adil

Re: electricity outage problem

o skid in >> broadside in a cloud of smoke,thoroughly used up, totally worn out, and >> loudly proclaiming “Wow! What a Ride!” - Hunter ThompsonDaemeon C.M. >> ReiydelleUSA (+1) 415.501.0198 <%28%2B1%29%20415.501.0198>London (+44) (0) >> 20 8144 9872 <%28%2B44%29%

Re: electricity outage problem

%20415.501.0198>London (+44) (0) 20 8144 9872 > <%28%2B44%29%20%280%29%2020%208144%209872>* > > On Fri, Jan 15, 2016 at 9:17 AM, Adil <adil.cha...@gmail.com> wrote: > >> Hi, >> we did full restart of the cluster but nodetool status still giving >> incoeren

migrating from 2.1.2 to 3.0.8 log errors

.Final.jar:4.0.23.Final] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101] we have installed java-8_101 anya idea what woud be the problem? thanks Adil does anyone

Re: migrating from 2.1.2 to 3.0.8 log errors

? Any idea? Thank Ad. Il 10/ago/2016 23:58, "Adil" <adil.cha...@gmail.com> ha scritto: > Thank you for your response, we have updated datastax driver to 3.1.0 > using V3 protocol, i think there are still some webapp that still using the > 2.1.6 java driver..we will upgra

Re: migrating from 2.1.2 to 3.0.8 log errors

10, 2016 at 10:33 AM, Adil <adil.cha...@gmail.com> wrote: > >> Hi guys, >> We have migrated our cluster (5 nodes in DC1 and 5 nodes in DC2) from >> cassandra 2.1.2 to 3.0.8, all seems fine, executing nodetool status shows >> all nodes UN, but i

Re: migrating from 2.1.2 to 3.0.8 log errors

just to share with you, by running rebuild_index the problem is solved. 2016-08-11 22:05 GMT+02:00 Adil <adil.cha...@gmail.com>: > After migrating C* from 2.1.2 to 3.0.8, all queries with the where > condition involved ad indexed column return zero rows for the old data, > instea

Re: Error while read after upgrade from 2.2.7 to 3.0.8

Hi, That means that some clients closes the connection, have you upgraded all clients? Il 30/set/2016 14:25, "Oleg Krayushkin" ha scritto: > Hi, > > Since the upgrade from Cassandra version 2.2.7 to 3.0.8 We're getting > following error almost every several minutes on

upgrading cassandra

Hi, we have a cluster with cassandra 3.0.9 and we are going to upgrade it to the latest version which i think is 3.11.3 but a teamate told me that the latest version is 3.0.17. what is the latest stable version? thanks in advance.