sstableloader prints nothing

2013-12-25 Thread Andrey Razumovsky
Hi everyone, I'm trying to use sstableloader to import large amounts of data into my cassandra-2.0.3 instance (single node). I've created sstables directory and not running sstableloader -d localhost path_to_tables but the process just starts and prints nothing at all! I've no idea whether it

Crash with TombstoneOverwhelmingException

2013-12-25 Thread Sanjeeth Kumar
Hi all, One of my cassandra nodes crashes with the following exception periodically - ERROR [HintedHandoff:33] 2013-12-25 20:29:22,276 SliceQueryFilter.java (line 200) Scanned over 10 tombstones; query aborted (see tombstone_fail_thr eshold) ERROR [HintedHandoff:33] 2013-12-25 20:29:22,278

Re: Crash with TombstoneOverwhelmingException

2013-12-25 Thread Rahul Menon
Sanjeeth, Looks like the error is being populated from the hintedhandoff, what is the size of your hints cf? Thanks Rahul On Wed, Dec 25, 2013 at 8:54 PM, Sanjeeth Kumar sanje...@exotel.in wrote: Hi all, One of my cassandra nodes crashes with the following exception periodically - ERROR

Re: sstableloader prints nothing

2013-12-25 Thread Andrey Razumovsky
OK, I figured that out - turns out that my sstables were in directory keyspace_name but not in keyspace_name/family_name. Would be great to have a proper error message here.. However, I still can't import the data. The exception I get on server now looks like this: WARN [STREAM-IN-/127.0.1.1]

Re: Crash with TombstoneOverwhelmingException

2013-12-25 Thread Edward Capriolo
I have to hijack this thread. There seem to be many problems with the 2.0.3 release. If this exception is being generated by hinted-handoff, I could understand where it is coming from. If you have many hints and many tombstones then this new feature interacts with the hint delivery process, in a

Re: Crash with TombstoneOverwhelmingException

2013-12-25 Thread Laing, Michael
It's a feature: In the stock cassandra.yaml file for 2.03 see: # When executing a scan, within or across a partition, we need to keep the # tombstones seen in memory so we can return them to the coordinator, which # will use them to make sure other replicas also know about the deleted rows.

Re: Cassandra unit testing becoming nearly impossible: suggesting alternative.

2013-12-25 Thread horschi
Hi Ed, my opinion on unit testing with C* is: Use the real database, not any embedded crap :-) All you need are fast truncates, by which I mean: JVM_OPTS=$JVM_OPTS -Dcassandra.unsafesystem=true and auto_snapshot: false This setup works really nice for me (C* 1.1 and 1.2, have not tested 2.0

Re: Cassandra unit testing becoming nearly impossible: suggesting alternative.

2013-12-25 Thread Joe Stein
I have been using vagrant (e.g. https://github.com/stealthly/scala-cassandra/ ) which is 100% reproducible across devs and test systems (prod in some cases). Also have a Docker setup too https://github.com/pegasussolutions/docker-cassandra . I have been doing this more and more with clients