Re: is it possible to disable compaction per CF ?

setMaxCompactionThreshold(0) setMinCompactionThreshold(0) 2012/7/27 Илья Шипицин > Hello! > > if we are dealing with append-only data model, so what if I disable > compaction on certain CF ? > any side effect ? > > can I do it with > > "update column family with compaction_strategy = null "

Re: restoring a counter

>>> a) how does that setting affect C* in a non-restoring start? > > renew_counter_id regenerates a new "NodeId" for the cassandra VM which > is used to keep track of the counter shards the node holds. If you > regenerate node ids on each restart, you will most likely corrupt your > counter data.

Re: Schema question : Query to support "Find which all of these 500 email ids have been registered"

What about if I spread these columns across 20 rows ? Then I have to query each of these 20 rows for 500 columns. but still this seems a better solution than one row for all cols or separate row for each email id approaches !? On Fri, Jul 27, 2012 at 11:36 AM, Aklin_81 wrote: > Sorry for the conf

Re: Questions regarding DataStax AMI

HI! I tried starting a cluster with Cluster started with these options: --clustername --totalnodes 3 --version community --release 1.0.8 But Cassandra's version is 1.1.2 Thanks *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 64097

Re: Unreachable node, not in nodetool ring

Hi again, Nobody has a clue about this issue ? I'm still facing this problem. Alain 2012/7/23 Alain RODRIGUEZ : > Does anyone knows how to totally remove a dead node that only appears > when doing a "describe cluster" from the cli ? > > I still got this issue in my production cluster. > > Alain

Re: Unreachable node, not in nodetool ring

nope my last ideas would be (and I am not sure these are the best) - try removetoken with -f option. I do not believe it will change anything but... - try nodeltool ring on ALL nodes and check all nodes see the unreachable node. If not, you could maybe juste decommission the one(s) that see the

Re: increased RF and repair, not working?

Dave, per my understanding of Yan's description he has 3 nodes and took one down manually to test; that should have worked, no? On Thu, Jul 26, 2012 at 11:00 PM, Dave Brosius wrote: > Quorum is defined as > > (replication_factor / 2) + 1 > therefore quorum when rf = 2 is 2! so in your case, both

Re: increased RF and repair, not working?

I think Dave is right, I have read this article again: http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/ I have data on two nodes, and "QUORUM read" means it need read from both two nodes. I guess I need to increase the RF to 3, to make the system can tolerance one node failure. thanks

Re: increased RF and repair, not working?

Ah! Yan I think you want your writes to use QUORUM and your reads to just be a single node right? If you need/want the read-repair, then I suppose you would need more nodes up (or deployed in your cluster) but if you are keeping 3 machines a RF of 2 with a write consistency of 2 and a read of 1 s

Re: Unsubscribe

http://wiki.apache.org/cassandra/FAQ#unsubscribe On Fri, Jul 27, 2012 at 9:46 AM, Samir Rayani wrote: > > -- Tyler Hobbs DataStax

Re: increased RF and repair, not working?

You have RF=2, CL= Quorum but 3 nodes. So each row is represented on 2 of the 3 nodes.If you take a node down, one of two things can happen when you attempt to read a row.The row lives on the two nodes that are still up. In this case you will successfully read the data.The row lives on one node

Re: Connection issue in Cassandra

On Thu, Jul 26, 2012 at 11:25 PM, Adeel Akbar wrote: > I used Cassandra 0.8.1 and pycasa 0.2. If I upgrade pycasa, then it have > compatibility issue. please suggest > You can use the latest version of pycassa with Cassandra 0.8. -- Tyler Hobbs DataStax

Re: increased RF and repair, not working?

Dave, What I was suggesting for Yan was to: WRITE: RF=2, CL=QUORUM READ: CL=ONE But you have a good pt... if he hits one of the replicas that didn't have the data, that would be bad. Thanks for clearing that up. On Fri, Jul 27, 2012 at 11:43 AM, Dave Brosius wrote: > You have RF=2, CL= Quorum

Re: Questions regarding DataStax AMI

Oh you're right, sorry about that. The concept of keeping older packages was recently implemented and while using --version community, you would need --release 1.0 in order to get 1.0.10. If you are using --version enterprise, you can use --release 2.0 to get DataStax Enterprise 2.0 which comes bu