Re: Error "evicting cold readers" when launching an EmbeddedCassandraService for a second time

2014-05-02 Thread DuyHai Doan
"What do you mean by truncating tables BTW?" "truncate table ;" in CQL3 I think truncating table is sufficient, as long as you do not run your tests in multi-threaded env. If multi-threaded env I would advise to randomize partition keys so the tests do not step over each other. If you wa

Re: Error "evicting cold readers" when launching an EmbeddedCassandraService for a second time

2014-05-02 Thread Clint Kelly
Hi Duy Hai, I was just trying to be extra-paranoid and to make sure that any screw up in one unit test did not at all affect the environment for my other unit tests. What do you mean by truncating tables BTW? Best regards, Clint On Thu, May 1, 2014 at 11:05 AM, DuyHai Doan wrote: > Hello C

Re: repair -pr does not return

2014-05-02 Thread Robert Coli
On Fri, May 2, 2014 at 12:29 AM, Jan Kesten wrote: > I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know, > routine repairs are still mandatory for handling tombstones - even I > noticed that the cluster now does a "snapshot-repair" by default. > > Now my cluster is running a

Re: Backup procedure

2014-05-02 Thread tommaso barbugli
In my tests compressing with lzop sstables (with cassandra compression turned on) resulted in approx. 50% smaller files. Thats probably because the chunks of data compressed by lzop are way bigger than the average size of writes performed on Cassandra (not sure how data is compressed but I guess it

Re: Cassandra slow on PasswordAuthenticator

2014-05-02 Thread Robert Coli
On Fri, May 2, 2014 at 10:00 AM, Patricia Gorla wrote: > The latency you're seeing is likely just the cost of using authentication. > To expand slightly, it's relatively likely that no one has done performance optimization of auth related code. 2 seconds seems "too long" for auth, I would probab

Re: Backup procedure

2014-05-02 Thread Robert Coli
On Fri, May 2, 2014 at 2:07 AM, tommaso barbugli wrote: > If you are thinking about using Amazon S3 storage I wrote a tool that > performs snapshots and backups on multiple nodes. > Backups are stored compressed on S3. > https://github.com/tbarbugli/cassandra_snapshotter > https://github.com/Jere

Re: Cassandra slow on PasswordAuthenticator

2014-05-02 Thread Patricia Gorla
Bhaskarjya, The latency you're seeing is likely just the cost of using authentication. Cheers, -- Patricia Gorla @patriciagorla Consultant Apache Cassandra Consulting http://www.thelastpickle.com

Re:

2014-05-02 Thread Patricia Gorla
Ebot, Could you share a bit more about what you are trying to achieve? CQL3 does have an analogy to dynamic columns, and you could potentially use collections (if your data isn't too large). Hard to say more without deta

Re: Some questions to adding a new datacenter into cassandra cluster.

2014-05-02 Thread Patricia Gorla
On Wed, Apr 30, 2014 at 10:21 AM, Arindam Barua wrote: > Since we don’t change the seeds configuration in the yaml files of DC1 and > DC2, how do DC1 and DC2 know the nodes in the DC3 if they reboot for some > reason later? Additional note: you want to have at least one seed node per availabili

Re: Backup procedure

2014-05-02 Thread Patricia Gorla
Artur, Replies inline. On Fri, May 2, 2014 at 10:42 AM, Artur Kronenberg < artur.kronenb...@openmarket.com> wrote: > we are running a 7 node cluster with an RF of 5. Each node holds about 70% > of the data and we are now wondering about the backup process. > What are you using for a backup proc

Re: *Union* data type modeling in Cassandra

2014-05-02 Thread DuyHai Doan
Hello Ngoc Minh I'd go with the first data model. To solve the null <-> tombstone issue, just do not insert them at runtime if value is null. If only numvalue double != null -> INSERT INTO data_table(key,numvalue) VALUES(...,...); If only numvalues list != null -> INSERT INTO data_table(key,nu

*Union* data type modeling in Cassandra

2014-05-02 Thread Ngoc Minh VO
Hello all, I don't know whether it is the right place to discuss about data modeling with Cassandra. We would like to have your feedbacks/recommendations on our schema modeling: 1. Our data are stored in a CF by their unique key (K) 2. Data type could be one of the following: Doubl

Re: Backup procedure

2014-05-02 Thread tommaso barbugli
If you are thinking about using Amazon S3 storage I wrote a tool that performs snapshots and backups on multiple nodes. Backups are stored compressed on S3. https://github.com/tbarbugli/cassandra_snapshotter Cheers, Tommaso 2014-05-02 10:42 GMT+02:00 Artur Kronenberg : > Hi, > > we are running

Backup procedure

2014-05-02 Thread Artur Kronenberg
Hi, we are running a 7 node cluster with an RF of 5. Each node holds about 70% of the data and we are now wondering about the backup process. 1. Is there a best practice procedure or a tool that we can use to have one backup that holds 100 % of the data or is it necessary for us to take mult

Re: repair -pr does not return

2014-05-02 Thread Artur Kronenberg
Hi, to be honest 2 days for 200GB nodes doesn't sound too unreasonable to me (depending on your hardware of course). We were running a ~20 GB cluster with regualr hard drives (no SSD) and our first repair ran a day as well if I recall correctly. We since improved our hardware and got it down t

Re: repair -pr does not return

2014-05-02 Thread Jan Kesten
Hi Duncan, is it actually doing something or does it look like it got stuck? 2.0.7 has a fix for a getting stuck problem. it starts with sending merkle trees and streaming for some time (some hours in fact) and then seems just to hang. So I'll try to update and see it that's solves the issu

Re: repair -pr does not return

2014-05-02 Thread Duncan Sands
Hi Jan, On 02/05/14 09:29, Jan Kesten wrote: Hello together, I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know, routine repairs are still mandatory for handling tombstones - even I noticed that the cluster now does a "snapshot-repair" by default. Now my cluster is runnin

repair -pr does not return

2014-05-02 Thread Jan Kesten
Hello together, I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know, routine repairs are still mandatory for handling tombstones - even I noticed that the cluster now does a "snapshot-repair" by default. Now my cluster is running a while and has a load of about 200g per n