RE: Multi-threaded sub-range repair

UPD: Here we can see that repair process can be executed in parallel: http://www.datastax.com/dev/blog/advanced-repair-techniques From: Plotnik, Alexey Sent: 24 февраля 2014 г. 12:42 To: user@cassandra.apache.org Subject: Multi-threaded sub-range repair 1. How many parallel threads is sa

Multi-threaded sub-range repair

1. How many parallel threads is safe to have for sub-range repair process running for a single node? 2. Is Repair process affected `concurrent_compactors` parameter? Should the `concurrent_compactors` meet the multithreaded repair process needs?

RE: Turn off compression (1.2.11)

It’s not wrong in case of economy, we have many TB of data, and it’s very expensive to have even 3TB per machine (we need 10TB minimum I think). The main thing you should understand – TB is not a problem, the problem is how many rows you have per node. From: Yogi Nerella [mailto:ynerella...@gmai

Re: Queuing System

Once schema I was thinking of was this: max.row.age: The producer will not write to this row after max row age, even if not full (e.g. 10 minutes) max.number.of.messages: Most messages that will ever be written to a row max.expire.time: TTL every column is written with set Queue[timeuuid][max.row

Re: Disabling opscenter data collection in Datastax community 2.0

Okay, I wasn't aware that I could use free version for production environments as well. I read somewhere on the datastax website it can be used only for testing/dev purposes otherwise I need to purchase. Here's a link(though quite dated) that confirms it: http://www.drdobbs.com/tools/datastax-serve

Re: Queuing System

Thanks Joe. That's a nice pointer. Will explore the possibility. I am just concerned about the Leader swap time window, but may be thats the tradeoff b/n data consistency Vs availability. Regards, Jagan On Sat, 22 Feb 2014 23:08:00 +0530 Joe Stein wrote Witho