Re: Cassandra 2.0 - AssertionError in ArrayBackedSortedColumns

This is a bug really: https://issues.apache.org/jira/browse/CASSANDRA-5786. This should get fixed in the next beta of 2.0, but if you really want to test CAS updates in the meantime, you'll have to provide the columns in (column family comparator) sorted order to the thrift cas() method. -- Sylva

Re: Cassandra 2.0 - AssertionError in ArrayBackedSortedColumns

Thanks for the reply Sylvain! A couple of follow-up questions: i. The second stack in my mail originated at a getRow() call. What could be the cause of that? I am assuming data retrieval should not cause any issues, unless data was stored in incorrect order and I don't know if that is possible thr

Re: Cassandra 2.0 - AssertionError in ArrayBackedSortedColumns

> unless data was stored in incorrect order and I don't know if that is > possible through the API.. > That's exactly what happens and that's why I say it's a bug. > > ii. I am also seeing some sporadic cases where a single column cas() > update is hitting this same issue (the bug you mentioned

Cassandra 2 vs Java 1.6

I know it was decided to drop the requirement for Java 1.6 for cassandra some time ago, but my question is should 2.0.0-beta1 run under java 1.6 at all ? I tried and got the following error: ma

Re: Cassandra 2 vs Java 1.6

I believe it won't run on 1.6. Java 1.7 is required to compile C* 2.0+ and once it's done, you cannot run it using Java 1.6 (this is what "Unsupported major.minor version" error tells you about; java version 50 is 1.6 and 51 is 1.7). M. W dniu 22.07.2013 10:06, Andrew Cobley pisze: I know it

Re: Cassandra 2.0 - AssertionError in ArrayBackedSortedColumns

Actually, your second stack trace is due to https://issues.apache.org/jira/browse/CASSANDRA-5788. On Mon, Jul 22, 2013 at 9:37 AM, Sylvain Lebresne wrote: > > unless data was stored in incorrect order and I don't know if that is >> possible through the API.. >> > > That's exactly what happens a

RE: Cassandra 2 vs Java 1.6

Actually, it looks like it may not compile under 1.6 either. build.xml has the following: BTW this came because I'm setting up a little test cluster on three spare mac computers in our labs. They haven't been updated for sometime and are running MacOs 10.6.8. Trying to install JDK 7u25 is

Re: Cassandra 2.0 - AssertionError in ArrayBackedSortedColumns

Thanks for the confirmation! It looks like the code is capable of handling the data in unsorted order with assertions disabled; so for the time being I will disable the assertion for my tests, until the fixes are available. Thanks, Soumava On Mon, Jul 22, 2013 at 1:33 AM, Sylvain Lebresne wrote

Strange cassandra-stress results with 2.0.0 beta1

I've been noticing some strange casandra-stress results with 2.0.0 beta 1. I've set up a single node on a Mac (4 gig ram, 2.8Ghz core 2 duo) and installed 2.0.0 beta1. When I run ./cassandra-stress -d 134.36.36.218 I'm seeing the interval-op-rate drop from a peek of 11562 at the start to 0 -2

R: Re: CL1 and CLQ with 5 nodes cluster and 3 alives node

Hi Aaron, thanks for your help. >If you have more than 500Million rows you may want to check the bloom_filter_fp_chance, the old default was 0.000744 and the new (post 1.) number is > 0.01 for sized tiered. I really don't think I have more than 500 million rows ... any smart way to count rows

sstable size change

Hi all, I know there has been several threads recently on this but I wanted to make sure I got a clear answer: we are looking to increase our SSTable size for a couple of our LCS tables as well as chunk size (to match the SSD block size). The largest table is at 500 GB across 6 nodes (RF

Re: Auto Discovery of Hosts by Clients

Thanks for you replies. Regards, Shahab On Sun, Jul 21, 2013 at 4:49 PM, aaron morton wrote: > Give the app the same nodes you have in the seed lists. > > Cheers > > - > Aaron Morton > Cassandra Consultant > New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 20/0

OPP seems completely unsupported in Cassandra 1.2.5

We were using 0.7.6 version. And upgraded to 1.2.5 today. We were using OPP (OrderPreservingPartitioner). OPP throws error when any node join the cluster. Cluster can not be brought up due to this error. After digging little deep, We realized that "peers" column family is defined with key as type

Cassandra Out of Memory on startup while reading cache

Hello, Since upgrading from 1.1.9 to 1.2.6 over the last week, we've had two instances where cassandra was unable, but kept trying to restart: SNIP INFO [main] 2013-07-19 16:12:36,769 AutoSavingCache.java (line 140) reading saved cache /var/cassandra/caches/SyncCore-CommEvents-KeyCache

Re: Re: CL1 and CLQ with 5 nodes cluster and 3 alives node

Do you have a copy of the specific stack trace? Given the version and CL behavior, one thing you may be experiencing is: https://issues.apache.org/jira/browse/CASSANDRA-4578 On Mon, Jul 22, 2013 at 7:15 AM, cbert...@libero.it wrote: > Hi Aaron, thanks for your help. > >>If you have more than 500M

Re: Cassandra Out of Memory on startup while reading cache

Sounds like this: https://issues.apache.org/jira/browse/CASSANDRA-5706, which is fixed in 1.2.7. /Janne On 22 Jul 2013, at 20:40, Jason Tyler wrote: > Hello, > > Since upgrading from 1.1.9 to 1.2.6 over the last week, we've had two > instances where cassandra was unable, but kept trying to

Re: sstable size change

I don't think upgradesstables is enough, since it's more of a "change this file to a new format but don't try to merge sstables and compact" -thing. Deleting the .json -file is probably the only way, but someone more familiar with cassandra LCS might be able to tell whether manually editing the

Cassandra 2.0 : Ant build issue

Hi, I'm working on a Mac OS 10.8 and trying to build the cassandra trunk using ant. I am getting the error as below. I can see a related bug that fixed a similar issue for debian ( https://issues.apache.org/jira/browse/CASSANDRA-5688), but I can still repro this on Mac. Thanks, Soumava soumava$

Re: sstable size change

My understanding is deleting the .json metadata file is the only way currently. If you search the user list archives, there are folks who are building tools to force compaction and rebuild sstables with the new size. I believe there's been a bit of talk of potentially including those tools as a pat

Re: Cassandra 2.0 : Ant build issue

On 07/22/2013 12:16 PM, Soumava Ghosh wrote: Hi, I'm working on a Mac OS 10.8 and trying to build the cassandra trunk using ant. I am getting the error as below. I can see a related bug that fixed a similar issue for debian (https://issues.apache.org/jira/browse/CASSANDRA-5688), but I can still

Re: Cassandra 2.0 : Ant build issue

I'm using 1.7.0_21 (not 25 though).. soumava$ java -version java version "1.7.0_21" Java(TM) SE Runtime Environment (build 1.7.0_21-b12) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) Thanks, Soumava On Mon, Jul 22, 2013 at 1:06 PM, Andrew Cobley wrote: > Are you using JDK 1.

Re: Cassandra 2.0 : Ant build issue

Are you using JDK 1.6. If so you'll need to get the 1.7 jdk (Java SE 7u25) from oracle to do the compile. See my message thread earlier today subject "Cassandra 2 vs Java 1.6 for a few more details. Andy On 22 Jul 2013, at 20:16, Soumava Ghosh mailto:soum...@cs.utexas.edu>> wrote: Hi, I'm

Re: Cassandra 2.0 : Ant build issue

Downloaded 1.7.0_25 and it still produces the following result: soumava$ git describe cassandra-2.0.0-beta1-100-ge0eacd2 soumava$ ant ... build-project: [echo] apache-cassandra: /Users/soumava/Documents/src/git-cassandra/build.xml [javac] Compiling 17 source files to /Users/soumava/Docum

RE: Cassandra 2.0 : Ant build issue

What version do you get with javac -version ? Andy From: soum...@utexas.edu [soum...@utexas.edu] on behalf of Soumava Ghosh [soum...@cs.utexas.edu] Sent: 22 July 2013 21:09 To: user@cassandra.apache.org Subject: Re: Cassandra 2.0 : Ant build issue I'm using 1.7

Re: Cassandra 2.0 : Ant build issue

On 07/22/2013 01:18 PM, Soumava Ghosh wrote: Downloaded 1.7.0_25 and it still produces the following result: soumava$ git describe cassandra-2.0.0-beta1-100-ge0eacd2 soumava$ ant ... build-project: [echo] apache-cassandra: /Users/soumava/Documents/src/git-cassandra/build.xml [javac]

Re: Cassandra 2.0 : Ant build issue

There you go: soumava$ javac -version javac 1.7.0_25 Thanks, Soumava On Mon, Jul 22, 2013 at 1:19 PM, Andrew Cobley wrote: > What version do you get with > > javac -version > > ? > Andy > > -- > *From:* soum...@utexas.edu [soum...@utexas.edu] on behalf of Soumava

RE: Cassandra 2.0 : Ant build issue

Hmm, I'm not sure then, I built 2.0 beta 1 earlier today with 1.7.0_25. One last thing, what have you got JAVA_HOME set to ? Andy From: soum...@utexas.edu [soum...@utexas.edu] on behalf of Soumava Ghosh [soum...@cs.utexas.edu] Sent: 22 July 2013 21:21 To: user

Re: Cassandra 2.0 : Ant build issue

Thanks Andrew! JAVA_HOME was the issue. It was not set, and I think that's why the build was somehow defaulting to /Library/Java/Home which was a 1.6 JDK. It should have been /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home. Setting JAVA_HOME to this path unblocked the build. If I

Re: Cassandra 2.0 : Ant build issue

On 07/22/2013 01:31 PM, Soumava Ghosh wrote: Thanks Andrew! JAVA_HOME was the issue. It was not set, and I think that's why the build was somehow defaulting to /Library/Java/Home which was a 1.6 JDK. It should have been /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home. Setting JAV

RE: Cassandra 2.0 : Ant build issue

>>If I may ask, isn't the Java setup supposed to update the environment >>variable? Sadly I don't think it does! Andy From: soum...@utexas.edu [soum...@utexas.edu] on behalf of Soumava Ghosh [soum...@cs.utexas.edu] Sent: 22 July 2013 21:31 To: user Subject: Re:

Re: sstable size change

You can remove the json file and that will be treated as all sstables are now in L0. Since you have lot of data, the compaction will take a very long time. See the comment below directly from Cassandra code. If you chose to do this, you might want to increase the rate of compaction by usual means.

cassandra 1.2.6 -> Start key's token sorts after end token

Hello, I am trying to figure what might be cause this error. I am using Cassandra 1.2.6 (tried with 1.2.3 as well) and I am trying to read data from cassandra on hadoop using column family input format. I also got the same error using pure astyanax on a test. I am using Murmur3Partitioner

how to find cassandra version using pycassa

I see only api version and schema version API available. Any idea Feng

Re: how to find cassandra version using pycassa

Cassandra's version itself is not available from the API. However, as you mention, describe_version provides the API version from which you could deduce the approximate version of Cassandra. You would just have to maintain this mapping yourself. On Mon, Jul 22, 2013 at 6:37 PM, F Q wrote: > I se

Re: memtable overhead

The way weve gone about our data models has resulted in lots of column families and just looking for guidelines about how much space each column table adds. TIA On Sun, Jul 21, 2013 at 11:19 PM, Darren Smythe wrote: > Hi, > > How much overhead (in heap MB) does an empty memtable use? If I have

Re: memtable overhead

Not sure how up-to-date this info is, but from some discussions that happened here long time ago I remember that a minimum of 1MB per Memtable needs to be allocated. The other constraint here is memtable_total_space_in_mb setting in cassandra.yaml, which you might wish to tune when having a lo