NPE in CompactionExecutor

I'm seeing a number of NullPointerExceptions in the log of my cluster. You can see the log line below. I'm thinking this is probably bad. Any ideas? ERROR [CompactionExecutor:38] 2013-07-19 17:01:34,494 CassandraDaemon.java (line 192) Exception in thread Thread[CompactionExecutor:38,1,main] j

[deletion in the future]

Hi guys, I've read here [1] that you can make a deletion mutation "for" the future. That mechanism operates as a schedule for deletions according to the stackoverflow post. But, I've been having problems to make it work with my thrift c++ client. I believe it's related to this paragraph of the thr

Auto Discovery of Hosts by Clients

Hello, I want my Thrift client(s) (using hector 1.1-3) to randomly connect to any node in the Cassandra (1.2.4) cluster. 1- One way is that I pass in a comma separated list of hosts and ports to the CassandraHostConfguration object. 2- The other option is that I configure the auto discovery of ho

Re: Auto Discovery of Hosts by Clients

With Auto discovery, you can provide the DC you are local to and it will only use hosts from that. On Fri, Jul 19, 2013 at 2:08 PM, Shahab Yunus wrote: > Hello, > > I want my Thrift client(s) (using hector 1.1-3) to randomly connect to any > node in the Cassandra (1.2.4) cluster. > > 1- One way

Re: sstable size ?

Awesome. Thanks Sylvain! On Jul 19, 2013 3:59 AM, "Sylvain Lebresne" wrote: > > (Commiter folks: this is helpful. @Sylvain - can you commit a patch >> under this ticket (or wherever): >> https://issues.apache.org/jira/browse/CASSANDRA-4766 - happy to >> review). >> > > > Right, should have done t

Re: Incorrect row data size

Some more data on this. It appears to happen specifically on large row compactions. My column families incorporate the new maps, and the maps get updated over time. could this be a bug? I previously ran into this: https://issues.apache.org/jira/browse/CASSANDRA-5677 and am running bits wit

Re: MailBox Impl

Great link, thanks. On Fri, Jul 19, 2013 at 9:40 AM, CharSyam wrote: > How about this: > http://www.elasticinbox.com/ > > 2013년 7월 19일 금요일에 Vegard Berget님이 작성: > > > Hi, > > 1) Counters will probably work for this. Our experience with counters > is that it is very accurate. But read up on h

Re: CPU Bound Writes

Kanwar, This is because writes are appends to the commit log, which is stored on disk, not memory. The commit log is then flushed to the memtable (in memory), before being written to an sstable on disk. So, most of the actions in sending out a write are writing to disk. Also see: http://www.data

CPU Bound Writes

"Insert-heavy workloads will actually be CPU-bound in Cassandra before being memory-bound" Can someone explain why the internals of why writes are CPU bound ?

Re: sstable size ?

> (Commiter folks: this is helpful. @Sylvain - can you commit a patch > under this ticket (or wherever): > https://issues.apache.org/jira/browse/CASSANDRA-4766 - happy to > review). > Right, should have done that sooner anyway. I've attached a rebased version to the ticket. Should get in soonish,

Re: MailBox Impl

How about this: http://www.elasticinbox.com/ 2013년 7월 19일 금요일에 Vegard Berget님이 작성: > Hi, > 1) Counters will probably work for this. Our experience with counters is that it is very accurate. But read up on how repair/inconsistencies etc is handled. > 2) You can not, as far as i know at least,

Re: MailBox Impl

Hi, 1)  Counters will probably work for this.  Our experience with counters is that it is very accurate.  But read up on how repair/inconsistencies etc is handled.2)  You can not, as far as i know at least, have ttl on part of a counter.  What you can do, depending on how accurate it needs to be, i