Looking for clarification on the gossip protocol... 3 random nodes every second?

Hi, I'm looking to get some clarification on how the gossip protocol works in Cassandra 2.0. Does a node contact 3 purely random nodes every second for gossip or is there more intelligence involved in how it selects the 3 nodes? *The Apache wiki on Cassandra states this:* "Gossip timer task runs

Re: Lots of deletions results in death by GC

Sorry to hear that Robert, I ran into similar issue a while ago. I had an extremely heavy write and update load, as a result Cassandra (1.2.9) was constantly flushing to disk and used to GC, tried exactly the same steps you tried (tuning memtable_flush_writers (to 2) and memtable_flush_queue_size (

Re: what tool will create noncql columnfamilies in cassandra 3a

I am also curious as to how users will manage Thrift-based tables without the cli. PyCassaShell comes to mind, as does using Thrift-based clients. On Tue, Feb 4, 2014 at 9:53 AM, Edward Capriolo wrote: > Cassandra 2.0.4 cli is informing me that it will no longer exist in the > next major. > > H

Re: Lots of deletions results in death by GC

Is it possible you are generating *exclusively* deletes for this table? On 5 February 2014 00:10, Robert Wille wrote: > I ran my test again, and Flush Writer's "All time blocked" increased to 2 > and then shortly thereafter GC went into its death spiral. I doubled > memtable_flush_writers (to 2

Re: Lots of deletions results in death by GC

On Tue, Feb 4, 2014 at 4:10 PM, Robert Wille wrote: > I would almost think that this is caused by high load on the server, but > I've never seen CPU utilization go above about two of my eight available > cores. If high load triggers this problem, then that is very disconcerting. > That means that

Re: Lots of deletions results in death by GC

I ran my test again, and Flush Writer¹s ³All time blocked² increased to 2 and then shortly thereafter GC went into its death spiral. I doubled memtable_flush_writers (to 2) and memtable_flush_queue_size (to 8) and tried again. This time, the table that always sat with Memtable data size = 0 now sh

Re: Cassandra 2.0 with Hadoop 2.x?

Hello Clint, Yes I was able to get it working after a bit of work. I have pushed the branch with the fix (which is currently quite a ways behind latest). You can compare to yours I suppose. Let me know if you have any questions. https://github.com/VerticalSearchWorks/cassandra/tree/Cassandra2-CDH

Re: Question 1: JMX binding, Question 2: Logging

JMX stuff is in /conf/cassandra-env.sh On Tue, Feb 4, 2014 at 2:25 PM, Kyle Crumpton (kcrumpto) wrote: > Hi all, > > I'm fairly new to Cassandra. I'm deploying it to a PaaS. One thing this > entails is that it must be able to have more than one instance on a single > node. I'm running into th

Re: Question 1: JMX binding, Question 2: Logging

Hello Kyle, For your first question, you need to create aliases to localhost e.g. 127.0.0.2,127.0.0.3 etc. this should get you going. About the logging issue, I think if your instance failing before it gets to long anything, as an example you can strart one instance and make sure it logs correctly.

Question 1: JMX binding, Question 2: Logging

Hi all, I'm fairly new to Cassandra. I'm deploying it to a PaaS. One thing this entails is that it must be able to have more than one instance on a single node. I'm running into the problem that JMX binds to 0.0.0.0:7199. My question is this: Is there a way to configure this? I have actually fo

Re: Data tombstoned during bulk loading 1.2.10 -> 2.0.3

Seems good. I'll discus it with data owners and we choose the best method. Best regards, Aleksander 4 lut 2014 19:40 "Robert Coli" napisał(a): > On Tue, Feb 4, 2014 at 12:21 AM, olek.stas...@gmail.com < > olek.stas...@gmail.com> wrote: > >> I don't know what is the real cause of my problem. We ar

Re: Cassandra 2.0 with Hadoop 2.x?

Hi, Look for posts from Thunder Stumpges in this mailing list. I know he has succeeded to make it Hadoop 2.x work with Cassandra 2.x For those who are interested in using it with Cassandra 1.2.13 you can use the patch https://github.com/cscetbon/cassandra/commit/88d694362d8d6bc09b3eeceb6baad7b

Re: Ultra wide row anti pattern

You could use another column of CAS as a management layer. You only have to consult it when picking up new rows. On Tue, Feb 4, 2014 at 3:45 PM, DuyHai Doan wrote: > Great idea for implementing queue pattern. Thank you Edward. > > However with your design there are still corner cases for 2 cons

Re: Ultra wide row anti pattern

Great idea for implementing queue pattern. Thank you Edward. However with your design there are still corner cases for 2 consumers to read from the same queue. Reading and writing with QUORUM does not prevent race conditions. I believe the new CAS feature of C* 2.0 might be useful here but with th

Re: Data tombstoned during bulk loading 1.2.10 -> 2.0.3

On Tue, Feb 4, 2014 at 12:21 AM, olek.stas...@gmail.com < olek.stas...@gmail.com> wrote: > I don't know what is the real cause of my problem. We are still guessing. > All operations I have done one cluster are described on timeline: > 1.1.7-> 1.2.10 -> upgradesstable -> 2.0.2 -> normal operations

Re: Ultra wide row anti pattern

Generally you need to make a wide row because the row keys in cassandra are ordered by their md5/murmer code. As a result you have no way of locating "new rows", but if the row name is predictable the columns inside the row are ordered. On Tue, Feb 4, 2014 at 12:02 PM, Yogi Nerella wrote: > Sor

Re: Ultra wide row anti pattern

Sorry, I am not understanding the problem, and I am new to Cassandra, and want to understand this issue. Why do we need to use wide row for this situation, why not a simple table in cassandra? todolist (user, state) ==> is there any other information in this table which needs for processing to

Re: Ultra wide row anti pattern

I have actually been building something similar in my space time. You can hang around and wait for it or build your own. Here is the basics. Not perfect but it will work. Create column family queue with gc_grace_period=[1 day] set queue [timeuuid()] ["z"+timeuuid()] = [ work do do] The producer

what tool will create noncql columnfamilies in cassandra 3a

Cassandra 2.0.4 cli is informing me that it will no longer exist in the next major. How will users adjust the meta data of non cql column families and other cfs that do not fit into the cql model? -- Sorry this was sent from mobile. Will do less grammar and spell check than usual.

Re: Keyspace directory not getting created in 1 machine

Hi Hari, On 04/02/14 10:38, Hari Rajendhran wrote: Dear Team , I have a 3 node cassandra 1.1.12 opensource version installed in our lab.The db files for columnfamilies are getting created in 2 machines while in one of the machine the data directory is empty.I have tried with the following opti

Keyspace directory not getting created in 1 machine

Dear Team , I have a 3 node cassandra 1.1.12 opensource version installed in our lab.The db files for columnfamilies are getting created in 2 machines while in one of the machine the data directory is empty.I have tried with the following option nodetool  -h [IP address of the not working ma

Maximum size and number of datafiles

Hello here, Is it possible to tell me if it possible to choose the maximum size for a datafile to prevent fs saturation. When cassandra choose to add a datafile ? Thanks 4 all your answears. Regards, Bonnet Jonathan.

Re: Data tombstoned during bulk loading 1.2.10 -> 2.0.3

I don't know what is the real cause of my problem. We are still guessing. All operations I have done one cluster are described on timeline: 1.1.7-> 1.2.10 -> upgradesstable -> 2.0.2 -> normal operations ->2.0.3 -> normal operations -> now normal operations means reads/writes/repairs. Could you plea