Jason,
Are you able document the steps to reproduce this on a clean install ?
Is so do you have time to create an issue on
https://issues.apache.org/jira/browse/CASSANDRA
Thanks
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 2
Joost,
Part of Jonathans explanation for flushing every approx 5 minutes was
to reduce the size of the commit log, and reduce the replay time.
Even with the patch flushing memtables is necessary at some point to
truncate the log. If this is an issue consider disabling durable_w
> The only thing I can think of is that the upgradesstables option follows a
> slightly different path to the bulk uploader when it comes to generating the
> sstables that have been flushed to disk?
Seems unlikely, they both run through the same classes which determine their
compression strategy v
Andy,
>>> I'm running Cassandra on Raspberry Pi (for educational reason) and have
Have you written about your experiences anywhere ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 3:02 AM, Andy Cobley wrote:
> I'v
Yes,
I've a number of (badly written I admit) blog posts at:
http://ac31004.blogspot.co.uk/
Andy
From: aaron morton
Reply-To:
Date: Wednesday, 4 July 2012 10:03
To:
Subject: Re: SnappyCompressor and Cassandra 1.1.1
Andy,
>>> I'm running Cassandra on Raspberry Pi (for educational reaso
> Do you have any ideas, advices on how to investigate in more details?
What sort of read queries are you sending ?
Are you using large multi gets ?
Are these servers under IO load ? / Is there a lot of compaction going on ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmort
It seems it was linked to "data volume".
The symptoms were :
- a read query is executed on a server (#3 in our case). this query is like
select from CF where A= and B= and C= and D= where A..D are secondary
indexes.
- #3 CPU increased a lot (CPU load around 20 for 8 cores).
During that time, clust
> select my_cf where columnA = a and columnB = b and columnC = c and columnD = d
Cassandra will only use one equality clause to select the candidate rows. The
other clauses are applied to the rows using that first clause.
The clause to use to select candidate rows is based on statistics that est
> Cassandra: 1.1.0-SNAPSHOT
Does it happen on an official release ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 4:53 AM, Owen Davies wrote:
> We are using hector.rb to do a MultigetSliceQuery over one row, with count 1.
>
Looks like it may have been overlooked when CF directories were added, can you
create a ticket on https://issues.apache.org/jira/browse/CASSANDRA
Thanks
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 1:15 AM, Pieter Callewaert wrote:
Try the data stax forums http://www.datastax.com/support-forums/
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 7:28 AM, Deno Vichas wrote:
> is the 2.1 image still around?
>
> On 7/2/2012 11:24 AM, Deno Vichas wrote:
>> all
> What accounts for the much larger virtual number? some kind of off-heap
> memory?
http://wiki.apache.org/cassandra/FAQ#mmap
> I'm a little puzzled as to why I would get such long pauses without swapping.
The two are not related. On startup the JVM memory is locked so it will not
swap, from t
It *may* have been compaction from the repair, but it's not a big CF.
I would look at the logs to see how much data was transferred to the node. Was
their a compaction going on while the GC storm was happening ? Do you have a
lot of secondary indexes ?
If you think it correlated to compaction
High CPU can be http://wiki.apache.org/cassandra/FAQ#ubuntu_hangs
memory usage looks ok http://wiki.apache.org/cassandra/FAQ#mmap
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 6:49 PM, Tamar Fraenkel wrote:
> Hi!
> I have
The Hector user group may be able to help
https://groups.google.com/forum/?fromgroups#!forum/hector-users
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 3/07/2012, at 7:06 PM, Alexey Shananin wrote:
> Hi All,
>
> We are currently testi
Many thx for the explanation Aaron.
On Wednesday, July 4, 2012, aaron morton wrote:
> > select my_cf where columnA = a and columnB = b and columnC = c and
> columnD = d
> Cassandra will only use one equality clause to select the candidate rows.
> The other clauses are applied to the rows using t
> We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core),
That's pretty small, try m1.xlarge.
> e are still not sure what version of thrift to use with Cassandra 1.0.7 (we
> are still getting the same message regarding the 'old client').
1.0.7 ships with thrift 0.6
What clie
Hello Aaron, thanks for your email.
- That's pretty small, try m1.xlarge.
Yes, this is small. We are aware of that, but that doesn't seem to be the
actual problem. But we cannot see any reason why this shouldn't work as a
test environment. After we get a fair understanding we are going to invest
We also get negative message lengths occasionally... Please see below:
ERROR 12:49:00,777 Thrift error occurred during processing of message.
org.apache.thrift.TException: Negative length: -2147483634
at
org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(TBinaryProtocol.java:388)
Hi @all,
since our upgrade form cassandra 1.0.3 to 1.1.0 the virtual memory usage
of the cassandra-nodes explodes
our setup is:
* 5 - centos 5.8 nodes
* each 4 CPU's and 8 GB RAM
* each node holds about 100 GB on data
* each jvm's uses 2GB Ram
* DiskAccessMode is standard, indexAccessMode is stan
Hi Dan,
We run RF 2 on RAID0 EBS drives. The reason we use EBS over on-instance
storage is two fold;
Firstly we have a relatively small cluster ( 4 nodes ), so we're quite
sensitive to any AWS issues (at the region level). If we had a larger
cluster then we would definitely use ephemeral storage
I was able to rule out that the Composite class from hector is causing
this issue. I opened up a ticket on this, please find it here:
https://issues.apache.org/jira/browse/CASSANDRA-4410
regards
On 29.06.2012 09:23, Sylvain Lebresne wrote:
> On Thu, Jun 28, 2012 at 6:43 PM, Henning Kropp wrote:
Thanks, we'll have a look.
--
Sylvain
On Wed, Jul 4, 2012 at 3:04 PM, Henning Kropp wrote:
> I was able to rule out that the Composite class from hector is causing
> this issue. I opened up a ticket on this, please find it here:
> https://issues.apache.org/jira/browse/CASSANDRA-4410
>
> regards
All of written below is my personal experience, as goals I wanted to achieve.
We use these parameters in PROD for GC logs:
JVM_OPTS="$JVM_OPTS -XX:+PrintGCTimeStamps"
JVM_OPTS="$JVM_OPTS -XX:+PrintGCDetails"
JVM_OPTS="$JVM_OPTS -Xloggc:/var/log/cassandra/gc-`date +%s`.log"
Log rotation works from
Thanks Aaron.
I wonder if it's possible to obtain columns from a CQL 3 select query
(with a select *) that aren't defined in the create table. These fields
are present when all attributes are loaded but not when using CQL3. Is
it the normal behavior? Thanks very much!
Thierry
Thanks for co
Thanks.
I thought my problems may be related to the second leap and I ran sudo date
-s "`date -u`" on all nodes. Things have improved much in the last 24 hours.
*Tamar Fraenkel *
Senior Software Engineer, TOK Media
[image: Inline image 1]
ta...@tok-media.com
Tel: +972 2 6409736
Mob: +972 54 8
On Jul 4, 2012 2:02 PM, "Vasileios Vlachos"
wrote:
>
> Any ideas what could be causing strange message lengths?
One cause of this that I've seen is a client using unframed Thrift
transport while the server expects framed, or vice versa. I suppose a
similar cause could be something that is not a T
Our Cassandra cluster consists of 8 nodes(16 core, 32G ram, 12G Heap,
1600Mb Young gen, cassandra1.0.5, JDK 1.7, 128 Concurrent writer
threads). The replication factor is 2 with 10 column families and we
service Counter incrementing write intensive tasks(CL=ONE).
I am trying to figure out the bott
We have modified maxTenuringThreshold from 1 to 5. May be it is causing
problems. Will change it back to 1 and see how the system is.
concurrent_compactors=8. We will reduce this, as anyway our system won't be
able to handle this number of compactions at the same time. Think it will
ease GC also t
29 matches
Mail list logo