Re: Ordering by multiple columns?

That's not just a bad idea but that's impossible. Any field that is part of primary key is immutable. You should read up the Cassandra documentation and understand the basics before start using it. Otherwise you could easily abuse it inadvertently. Praveen On Oct 10, 2016, at 6:22 PM, Ali

Re: Running Cassandra in Integration Tests

is the config in a temp location - wouldn't it be better to put it in src/test/resources and try to specify that? Thanks. On Fri, Oct 7, 2016 at 6:17 AM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Honestly there isn't much code to share. Here is the code (exc

Re: Running Cassandra in Integration Tests

7, 2016 at 6:17 AM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Honestly there isn't much code to share. Here is the code (excluded exception handling). For yaml location, we have the classpathpath and write to temp location everytime. System.setProperty(&

Re: Running Cassandra in Integration Tests

ing Cassandra in Integration Tests Peddi @ Amazon, would you be able to share your code such as in a gist, if possible, please? Also, which version of cassandra are you doing that with? On Fri, Oct 7, 2016 at 5:41 AM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: We could no

Re: Running Cassandra in Integration Tests

We could not use cassandra unit for licensing reasons so we ended up instantiate CassandraDeamon after setting system property of cassandra.config={yaml location}. It works fine for our needs. Praveen From: Ali Akhtar > Reply-To:

Re: how to start a embed cassandra instance?

We do something similar by starting CassandraDaemon class directly (you would need to provide a yaml file though). You can start and stop CassandraDaemon class from your unit test (typically @BeforeClass). Praveen On Jul 12, 2016, at 3:30 AM, Stone Fang

Re: auto_boorstrap when a node is down

alonso.com/cassandra-instantaneous-in-place-node-replacement/ We've been using it for a while and works nicely and avoids the time, resources and baby-sitting consumption of streaming data across nodes. Regards Carlos Alonso | Software Engineer | @calonso<https://twitter.com/calonso&g

Re: auto_boorstrap when a node is down

omething like this happening will decrease, but it may still happen. If this is not a problem you may use option -Dcassandra.consistent.rangemovement=false to bootstrap a node when another node is down. See CASSANDRA-2434 for more background. 2016-03-30 11:14 GMT-03:00 Peddi, Praveen <

auto_boorstrap when a node is down

Hello all, We just upgraded to 2.2.4 (from 2.0.9) and we noticed one issue when new nodes are added. When we add a new node when no nodes are down in the cluster, everything works fine but when we add new node while 1 node is down, I am seeing following error. My understanding was when

Re: Removing Node causes bunch of HostUnavailableException

f so, I could use a status update and more information about the remaining issues. C*heers, --- Alain Rodriguez - al...@thelastpickle.com<mailto:al...@thelastpickle.com> France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2016-03-04 19:39 GMT+

Re: Removing Node causes bunch of HostUnavailableException

few minutes. -- Jack Krupansky On Thu, Mar 3, 2016 at 4:40 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Hi Jack, Which node(s) were getting the HostNotAvailable errors - all nodes for every query, or just a small portion of the nodes on some queries?

Re: Removing Node causes bunch of HostUnavailableException

provider). Could that be the reason for these failures? If a dead node is in the seed nodes list and we try to remove that node, could that lead to blip of failures. The failures don’t last for more than few minutes. -- Jack Krupansky On Thu, Mar 3, 2016 at 4:16 PM, Peddi, Praveen <pe...@amazon.

Re: Removing Node causes bunch of HostUnavailableException

- Alain Rodriguez - al...@thelastpickle.com<mailto:al...@thelastpickle.com> France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2016-03-02 22:17 GMT+01:00 Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>>: Hi Robert, Thanks for you

Re: Removing Node causes bunch of HostUnavailableException

cassandra.apache.org>> Subject: Re: Removing Node causes bunch of HostUnavailableException On Wed, Mar 2, 2016 at 8:10 AM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: We have few dead nodes in the cluster (Amazon ASG removed those thinking there is an issue with health). Now we are

Re: "Not enough replicas available for query" after reboot

Are you able to run queries using cqlsh with consistency ALL? On Feb 4, 2016, at 6:32 PM, Flavien Charlon > wrote: No, there was no other change. I did run "apt-get upgrade" before rebooting, but Cassandra has not been upgraded. On 4

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

en The same buffer size is used by compressed reads as well, but tuned with compression_chunk_size table property. It’s likely true that if you lower compression_chunk_size, you’ll see improved read performance. This was covered in the AWS re:Invent youtube link I sent in my original reply. From: &

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Re: Slow performance after upgrading from 2.0.9 to 2.1.11 On Fri, Jan 29, 2016 at 12:30 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: > > Hello, > We have another update on performance on 2.1.11. compression_chunk_size > didn’t really help muc

Re: compaction throughput

That is interesting... We recently resolved a performance issue solely by increasing concurrent_compactors parameter from default to 64. We have two tables but 90% data is only in 1 table. We got read performance boost of more than 100% just by increasing that param in yaml. Based on what you

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

earch "Read is slower in 2.1.6 than 2.0.14" in this forum, you can find another thread I sent a while ago. The perf test I did indicated that read is slower for 2.1.6 than 2.0.14 so we stayed with 2.0.14. On Tue, Jan 12, 2016 at 9:35 AM, Peddi, Praveen <pe...@amazon.com<m

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

uary 7, 2016 at 1:01 AM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>, Peddi Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> Subject: Re: Slow performance after upgradin

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

.org<mailto:user@cassandra.apache.org>> Date: Wednesday, January 6, 2016 at 3:49 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Slow performance after upgrading

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

and see if it's any better. Praveen On Jan 6, 2016, at 6:07 PM, Michael Shuler <mich...@pbandjelly.org<mailto:mich...@pbandjelly.org>> wrote: On 01/06/2016 03:57 PM, Peddi, Praveen wrote: This blog <http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-faster> claims C

Slow performance after upgrading from 2.0.9 to 2.1.11

Hi, We have upgraded Cassandra from 2.0.9 to 2.1.11 in our loadtest environment with pretty much same yaml settings in both (removed unused yaml settings and renamed few others) and we have noticed performance on 2.1.11 is worse compared to 2.0.9. After more investigation we found that the

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

he.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 On Wed, Jan 6, 2016 at 11:41 AM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: We have upgraded Cassandra from 2.0.9 to

Overriding timestamp with light weight transactions

Hi, We are using Cassandra 2.0.9 and we currently have "using timestamp" clause in all our update queries. We did this to fix occasional issues with ntp drift on AWS. We recently introduced conditional update in couple of our API and we realized that I can't have "using timestamp" and "if

Re: Overriding timestamp with light weight transactions

real world problem of clock variance. If you understand that you've got clocks that are going to be more than 10ms off, and you're issuing queries within a few ms of each other, why do you think that your custom supplied timestamps are going to be correct? On Nov 16, 2015, at 1:01 PM, Peddi, Prav

Re: Overriding timestamp with light weight transactions

apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Overriding timestamp with light weight transactions Perhaps you should fix your clock drift issues instead of trying to use a workaround? On Nov 16, 2015, at 11:39 AM, Peddi, Praveen <pe..

Re: Overriding timestamp with light weight transactions

s definitely a consistency risk anyway, as I understand it, since the 'latest' one wins and could easily be lurking in a hint somewhere etc. On Mon, Nov 16, 2015 at 4:27 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Jon, Thanks for your response. Our custom supplied ti

Re: Deletes Reappeared even when nodes are not down

t 5:57 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Deletes Reappeared even when nodes are not down On Fri, Nov 13, 2015 at 1:47 PM, Peddi, Praveen <pe...@amazon.com&l

Re: Deletes Reappeared even when nodes are not down

wn Well, yeah, it's still possible. Are your clocks 20 minutes off? On Nov 13, 2015, at 1:20 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Hi Jon, Thanks for your response. Clock skews is not a possibility because the row that got re-appeared is 20 mins older

Re: Deletes Reappeared even when nodes are not down

org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Deletes Reappeared even when nodes are not down On Fri, Nov 13, 2015 at 1:09 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: We

Deletes Reappeared even when nodes are not down

Hi, We are using Cassandra 2.0.8, with replication factor of 3. We are seeing a scenario where some of the rows in the table reappears even after they are deleted. We have seen this in Prod 3 times in last 1 week and coincidentally all 3 times on the same partition. We have confirmed that nodes

Re: Deletes Reappeared even when nodes are not down

ssandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Deletes Reappeared even when nodes are not down Any chance your clocks are off? On Nov 13, 2015, at 1:09 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>

CQL error when adding multiple conditional update statements in the same batch

Hi, I am trying to understand this error message that CQL is throwing when I try to update 2 different rows with different values on same conditional columns. Doesn't CQL support that? I am wondering why CQL has this restriction (since condition applies to each row independently, why does CQL

Re: CQL error when adding multiple conditional update statements in the same batch

Sorry Cassandra 2.0.9 (I was using 2.0.8 but there was another bug in 2.0.8 so upgraded to 2.0.9) On Oct 8, 2015, at 4:43 PM, Peddi, Praveen <pe...@amazon.com<mailto:pe...@amazon.com>> wrote: Cassandra 2.0.8. From: Tyler Hobbs <ty...@datastax.com<mailto:ty...@da

Re: CQL error when adding multiple conditional update statements in the same batch

f that check didn't work properly for batch statements in 2.0. On Thu, Oct 8, 2015 at 3:22 PM, sai krishnam raju potturi <pskraj...@gmail.com<mailto:pskraj...@gmail.com>> wrote: could you also provide the columnfamily schema. On Thu, Oct 8, 2015 at 4:13 PM, Peddi, Praveen <p