Re: NetworkTopology

Hello, Yes you are right AFAIK. On 1 March 2013 02:19, Kanwar Sangha wrote: > Hi – Quick question. When specifying the replication across 2 DCs, can > we have 1 replication factor across 2 Data centres ? Does the below mean > that there will be 2 copies of the data , 1 in DC1 and 1 in DC2 ?**

CQL3 and counters

Greetings. On this document: http://cassandra.apache.org/doc/cql3/CQL.html#updateStmt …I read, under UPDATE section, that: "The c = c + 3 form of is used to increment/decrement counters. The identifier after the ‘=’ sign must be the same than the one before the ‘=’ sign (Only increment/dec

Unable to instantiate cache provider org.apache.cassandra.cache.SerializingCacheProvider

This happened sometime ago, but for the sake of helping others if they encounter, each column family has a row cache provider, you can read into the schema, for example : ... and row_cache_provider = 'SerializingCacheProvider' ... it cannot start the cache provider for a reason and as a result,

Re: Other nodes are seen down with rpc_address 0.0.0.0 in version 1.2.2

Yes, it's caused by bug described in CASSANDRA-5299. It's because PropertyFileSnitch is using RPC address to obtain DC name from cassandra-topology.properties file. As you use 0.0.0.0 for RPC and this IP cannot be found in this config file, C* crashes. M. W dniu 01.03.2013 10:43, Jean-Armel L

Re: Other nodes are seen down with rpc_address 0.0.0.0 in version 1.2.2

Hi Michal, Thanks for your quick answer. I am going to apply the patch defined in CASSANDRA-5299. Regards. Jean Armel

Re: -pr vs. no -pr

On Fri, Mar 1, 2013 at 12:39 AM, Hiller, Dean wrote: > Isn't it true if I have 6 nodes, I could run nodetool repair on just 2 > nodes(RF=3) instead of using nodetool repair –pr??? > > What is the advantage of –pr then? I think the main advantage of nodetool is that you don't have to calculate /

Re: CQL3 and counters

> > On C* 1.2.1 I see that the following query works: > >update counters set value=value+5 where owner_id='1' and > counter_type='trash'; > > ...while the following one gives an error (Bad Request: Invalid > non-counter operation on counter table): > >update counters set value=5 where owner

Re: CQL3 and counters

"DO *NOT* USE THAT!!!" Crystal clear ;-). Thanks for the warning. Alain 2013/3/1 Sylvain Lebresne > On C* 1.2.1 I see that the following query works: >> >>update counters set value=value+5 where owner_id='1' and >> counter_type='trash'; >> >> ...while the following one gives an error (Ba

Re: -pr vs. no -pr

On Thu, Feb 28, 2013 at 11:39 PM, Hiller, Dean wrote: > Isn't it true if I have 6 nodes, I could run nodetool repair on just 2 > nodes(RF=3) instead of using nodetool repair –pr??? > Yes, it is true. And to precise further, in your case you have 2 options: 1) doing repair *without* -pr on 2 no

Re: -pr vs. no -pr

Sweeet, I %100 understand this now from these last few emails. It has always been a bit confusing. Thanks, Dean From: Sylvain Lebresne mailto:sylv...@datastax.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Date: Friday, March 1,

CQL3 to ORDER BY Verification

My ColumnFamily is defined as follows: CREATE TABLE UserProfileHistory( username text, timestamp bigint, -- millis since epoch data text, -- JSON PRIMARY KEY (username, timestamp) ) WITH CLUSTERING ORDER BY (timestamp DESC); Each insert on the username adds to the wide row. The

Re: CQL3 to ORDER BY Verification

On Fri, Mar 1, 2013 at 5:16 PM, Adam Venturella wrote: > My ColumnFamily is defined as follows: > > > CREATE TABLE UserProfileHistory( > username text, > timestamp bigint, -- millis since epoch > data text, -- JSON > PRIMARY KEY (username, timestamp) > ) WITH CLUSTERING ORDER BY (t

Re: no other nodes seen on priam cluster

Thanks a lot Ben, actually I managed to make it work erasing the SimpleDB Priam uses to keeps instances... I would pulled the last commit from the repo, not sure if it helped or not. But you message made me curious about something... How do you do to add more Cassandra nodes on the fly? Just upda

Re: CQL3 to ORDER BY Verification

Perfect! Thanks for the response Sylvain! On Friday, March 1, 2013, Sylvain Lebresne wrote: > On Fri, Mar 1, 2013 at 5:16 PM, Adam Venturella > > > wrote: > >> My ColumnFamily is defined as follows: >> >> >> CREATE TABLE UserProfileHistory( >> username text, >> timestamp bigint, -- mill

upgrade 1.1.4 to 1.2.2 around 120x performance loss(one node only)

I setup a QA system copying our production system which was accidentally SimpleSnitch I found out but we are only in one datacenter right now luckily. I have 4 nodes on 1.1.4 and I ran the following commands to upgrade ONE SINGLE NODE to 1.2.2 #on the node itself nodetool drain nodetool -h loca

Re: upgrade 1.1.4 to 1.2.2 around 120x performance loss(one node only)

No. I've actually found performance is better. Sounds like a timeout somewhere. On Mar 1, 2013, at 10:18 AM, "Hiller, Dean" wrote: > I setup a QA system copying our production system which was accidentally > SimpleSnitch I found out but we are only in one datacenter right now luckily. > > I ha

Re: upgrade 1.1.4 to 1.2.2 around 120x performance loss(one node only)

Ignore, found out this seems to be astyanax related as the cassandra-cli is lightning quick. Dean From: , Nrel mailto:dean.hil...@nrel.gov>> Date: Friday, March 1, 2013 11:18 AM To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Subject: upgrade

exception from cassandra on upgrade (exc from older version)

I am getting different exceptions in cassandra on upgrades… (these exceptions are on my 1.1.4 node though!!! Caused I think by my upgrade to 1.2.2 thankfully in QA though). How can I rolling upgrade my entire cluster if this is going to occur in production I bet as well? INFO [CompactionExecut

Re: CQL3 and counters

Don't delete them either! On Friday, March 1, 2013, Alain RODRIGUEZ wrote: > "DO *NOT* USE THAT!!!" > > Crystal clear ;-). Thanks for the warning. > > Alain > > 2013/3/1 Sylvain Lebresne >>> >>> On C* 1.2.1 I see that the following query works: >>> >>>update counters set value=value+5 where o

reading the updated values

hi, i m trying to use cassandra as main data-store and elasticsearch for realtime quries. my question is how do i get the updated data in cassandra for last 1 hour or so to be indexed in elasticsearch. once i get the updated data from cassandra i can index that to ES. is there any specific