This is a cluster of 2 nodes, each having 8G of operating memory,
replicationfactor=2
Write/read pressure is quite low and almost never exceeds 10/second
>From time to time (2-3 times in a month) I see GC activity in logs and for
>this time cassandra stops responding to requests which results i
I have similar problem with cassandra 0.8.10. After digging a while
I've found that my problem is somehow related to system page scanning
activities.
After turning on -Xloggc I've found high system cpu usage during
ParNew. After looking into sar -B I've found this:
08:00:08 AM pgpgin/s pgpgout/s
Is the "Threads" in your data the number of clients? How much heap space
does each node have?
YCSB has a paper on their benchmark tests. You can try comparing your
result with theirs and see if you have similarity.
Best regards,
Manoj
On Tuesday, July 17, 2012, Code Box wrote:
> I am doing Cas
Hello!
is it possible to write CQL statement for creation of ColumnFamily in
"create if not exists" manner ?
or "create or update" manner ?
Cheers,
Ilya Shipitsin
When they say "linear scalibility" they mean "throughput scales with the
amount of machines in your cluster".
Try adding more machines to your cluster and measure the thoughput. I'm
pretty sure you'll see linear scalibility.
regards,
Christian
On Tue, Jul 17, 2012 at 6:13 AM, Code Box wrote:
FSync = Batch and Window = 0ms is expected to give relatively crappy
result. It means C* will fsync on disk pretty much all write. This is an
overly safe setting and no database with that kind of setting will perform
correctly because you're far too much bound by the hard drive.
If you want strong
Hi
I have a 4 nodes Cassandra cluster, and replicate factor is 3, and write
consistent level is ALL, and each write suppose to write to at least 3
nodes, right?
I check the schema, and found the parameter "Replicate on write: false",
what does this parameter mean.
How it impact the writ
On Tue, Jul 17, 2012 at 5:05 PM, Jason Tang wrote:
>I check the schema, and found the parameter "Replicate on write: false",
> what does this parameter mean.
First, that parameter only affects counter increments, it has no
impact whatsoever on normal writes.
For counters, if set to false as
Hello all!
I'm new to Cassandra and the list. Still learning and testing basic stuff. I've
got a couple of questions which I'm hoping you could help me with.
I'm currently using Cassandra 1.1.1 and CQL Spec 3.
My schema consists of a table which represents a user list with with their
accordin
Thanks a lot for your reply guys. I was trying fsyn = batch and window =0ms
to see if the disk utilization is happening full on my drive. I checked the
numbers using iostat the numbers were around 60% and the CPU usage was
also not too high.
Configuration of my Setup :-
I have three m1.xlarge ho
Hello all,
There is a lot of material on Replication factor and Consistency level but I
am a little confused by what is happening on my setup. (Cassandra 1.1.2). I
would appreciate any answers.
My Setup: A cluster of 2 nodes evenly balanced. My RF =2, Consistency Level;
Write = ANY and Read = 1
Looking for ideas on how to diagnose this issue. I have installed v1.1.2 on
a two-node cluster (the data files loaded, incidentally, were from an
earlier v1.1.1 2-node setup). While initially I recall being able to
create/drop column families, I am no longer able to.
Let's say I have column fa
Thanks for your suggestion however, I am still unable to build 1.1.2.
I have found a version of antlr and libantlr installed by apt which
then I removed them, but that did not resolve the issue. After some
digging in Google, I found some people having similar problems with
antlr and they had sugges
Hi
I am starting using Cassandra for not a long time, and also have problems
in consistency.
Here is some thinking.
If you have Write:Any / Read:One, it will have consistency problem, and if
you want to repair, check your schema, and check the parameter "Read repair
chance: "
http://wiki.apache.o
Thanks..but write ALL will fail for any downed nodes. I am thinking of
QUORAM.
From: Jason Tang [mailto:ares.t...@gmail.com]
Sent: Tuesday, July 17, 2012 8:24 PM
To: user@cassandra.apache.org
Subject: Re: Replication factor - Consistency Questions
Hi
I am starting using Cassandra for n
truncate requires all all nodes to be available.
Let us know when you have the full error.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 17/07/2012, at 10:04 AM, Guy Incognito wrote:
> sorry i don't have the exact text right now but it
Assuming all the memory and yaml settings default that does not sound right.
The first thought would be the memory meter not counting correctly...
Do you do a lot of deletes ?
Do you have a lot of CF's and/or secondary indexes ?
Can you see log lines about the "liveRatio" for your cf's ?
I
It's not in the language as it stands.
If you would like to see it add a request to
https://issues.apache.org/jira/browse/CASSANDRA and maybe help out :)
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 18/07/2012, at 1:14 AM, Илья Шипицин
> the data... basically each row will represent a country, and each column of a
> particular row will represent the data of a single user.
Almost.
The first field in the composite primary key is the row key, the remaining
fields are used to prefix the column names. So each column will be a sing
I would benchmark a default installation, then start tweaking. That way you can
see if your changes result in improvements.
To simplify things further try using the tools/stress utility in the cassandra
source distribution first. It's pretty simple to use.
Add clients until you see the latenc
The cassandra stress tool gives me values around 2.5 milli seconds for
writing. The problem with the Cassandra Stress Tool is that it just gives
the average latency numbers and the average latency numbers that i am
getting are comparable in some cases. It is the 95 percentile and 99
percentile numb
Yes, for ALL, it is not good for HA, and because we meet problem when use
QUORAM, and current solution is switch Write:QUORAM / Read:QUORAM when got
"UnavailableException" exception.
2012/7/18 Jay Parashar
> Thanks..but write ALL will fail for any downed nodes. I am thinking of
> QUORAM.
>
>
22 matches
Mail list logo
