Aaron,
I added -Dcassandra.load_ring_state=false in the cassandra-env.sh and did a
rolling restart With one node in 1.2.3 version and 11 other nodes in
1.1.10, the 1.1.10 nodes saw 1.2.3 node but now the gossip on 1.2.3 only
sees itself.
Cheers,
-Arya
On Thu, Mar 28, 2013 at 1:02 PM, Arya Gouda
Hi,
I just wanted to share our experience of upgrading 1.0.10 to 1.2.3. It
happened that first we upgraded both of our two seeds to 1.2.3. And
basically after that old nodes couldn't communicate with new ones
anymore. Cluster was down until we upgraded all nodes to 1.2.3. We don't
have many n
On Mon, Apr 1, 2013 at 10:19 PM, aaron morton wrote:
> ERROR [Thread-232] 2013-04-01 22:22:21,760 CassandraDaemon.java (line
> 133) Exception in thread Thread[Thread-232,5,main]
> java.lang.IndexOutOfBoundsException: index (2) must be less than size (2)
>at
> com.google.common.base.Precond
Hello,
I try to read, edit, write and re-read a cassandra-yaml-config file
programmatically, but this unfortunately does not work as expected:
Here is my example:
/* start */
package com.fue;
import java.io.*;
import org.apache.cassandra.config.*;
import org.apache.cassandra.utils.SkipNullR
I just tried to use this setting (I'm using 1.1.9). And it appears I can't
set min > 32, as that's the max max now (using nodetool at least). Not
sure if JMX would allow more access, but I don't like bypassing things I
don't fully understand. I think I'll just leave my compaction killers
running
Edward, you make a good point, and I do think am getting closer to having
to increase my cluster size (I'm around ~300GB/node now).
In my case, I think it was neither. I had one node OOM after working on a
large compaction but it continued to run in a zombie like state (constantly
GC'ing), which
Settings do not make compactions go away. If your compactions are "out of
control" it usually means one of these things,
1) you have a corrupt table that the compaction never finishes on,
sstables count keep growing
2) you do not have enough hardware to handle your write load
On Tue, Apr 2, 2013
Hi Aaron,
I will try to slow down the compaction. Since this is our DEV environment
the core problem remains as we just have 2 cores. I will get back in case I
see any different situation.
Thank you for your inputs.
Thanks,
Jay
On Sun, Mar 31, 2013 at 5:35 AM, aaron morton wrote:
> > How thi
Hi, Aaron!
We were using 1.2.2. Now after your suggestion I've upgraded it to 1.2.3.
That *CorruptSSTableException* is now gone, but the problem is still here -
after some time we start getting another exception in cassandra logs (and
transport exception on the client side). The new exception is
*
Oh, JBOD, not JBOB.
no, we were using RAID 5 and RAID 6 from what I understand. I am trying to get
a test run with just one disk to make sure the test is correct as one disk
should have much less performance than 20 in the case of random access. In
sequential, I think performance would be the
Is 1.2 JBOB and april fools joke? Heh, seriously though, I have no idea what
you are talking about there. I am trying to get raw disk performance with no
cassandra involved before involving cassandra…..which is the next step.
Thanks,
Dean
From: aaron morton mailto:aa...@thelastpickle.com>>
Re
We ran into some similar errors in playorm development. Basically, you
defined a composite probably but are not correctly using that composite.
I am not sure about queries though as we had the issue when saving data
(ie. Using deviceID+deviceName did not work and we had to create an full
blown com
Thanks Gregg & Aaron. Missed that setting!
On Tuesday, April 2, 2013, aaron morton wrote:
> Set the min and max
> compaction thresholds for a given column family
>
> +1 for setting the max_compaction_threshold (as well as the min) on the a
> CF when you are getting behind. It can limit the size o
column family created using CQL is not visible via Cassandra CLI
[default@test1] list employees1;
employees1 not found in current keyspace.
CQL3 automatically down-cases all unquoted literals
You need to enclose any name with mixed case in quotes - see
http://stackoverflow
I didn't launched these commands when in troubles, next time I will. For
now here is what I have (this is working properly for now).
$mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun Mar 17 01:46:05 2013
Raid Level : raid0
Array Size : 1761459200 (1679.86 GiB
http://www.stuntlist.com/includes/likeit.php?xvsqbmy712itdfg
**
Michael's new single is entitled Scream, which, coincidentally, is exactly what
p
Thanks for reply, Aaron. Unluckily, I think it's not the case - we did
some quick tests last week and for now it _seems_ that:
1) There was no empty / zero-lenght key in data we loaded - that was the
first thing we checked
2) By "bisecting" the data, we found out that the row that makes the
pr
17 matches
Mail list logo
