Not really
What version are you on? Do you have pending compactions and no ongoing
compactions?
/Marcus
On Wed, Sep 24, 2014 at 11:35 PM, Donald Smith
donald.sm...@audiencescience.com wrote:
On one of our nodes we have lots of pending compactions (499).In the
past we’ve seen pending
Increase heap size with Cassandra and try
On 25/09/2014 3:02 am, Prem Yadav ipremya...@gmail.com wrote:
BTW, thanks Michael.
I am surprised why I didn't search for Cassandra oom before.
I got some good links that discuss that. Will try to optimize and see how
it goes.
On Wed, Sep 24, 2014
Hi All,
I am using cassandra with Pentaho PDI kettle, i have installed cassandra in
Amazon EC2 instance and in local-machine, so when i am trying to retrieve
data from local machine using Pentaho PDI it is taking few seconds (not
more then 20 seconds) and if i do the same using production
Thanks,
It seems that I was not clear in my question, I would like to store values
in the column name, for example column.name would be event_name
(temperature) and column-content would be the respective value (e.g.
40.5) . And I need to know how the schema should look like in CQL 3
best,
/Shahab
You'll need to provide a bit of information. To start, a query trace
from would be helpful.
http://www.datastax.com/documentation/cql/3.0/cql/cql_reference/tracing_r.html
(self promo) You may want to read over my blog post regarding
diagnosing problems in production. I've covered diagnosing
Version 2.0.9. We have 11 ongoing compactions on that node.
From: Marcus Eriksson [mailto:krum...@gmail.com]
Sent: Thursday, September 25, 2014 12:45 AM
To: user@cassandra.apache.org
Subject: Re: Would warnings about overlapping SStables explain high pending
compactions?
Not really
What
We have large boxes with 256G of RAM and SSDs. From iostat, top, and sar
we think the system has excess capacity. Anyone have recommendations about
multihominghttp://en.wikipedia.org/wiki/Multihoming cassandra on such a node
(connecting it to multiple IPs and running multiple cassandras
Doing this seems counter-productive to Cassandra's design/use-cases. It's
best at home running on a large number of smaller servers rather than a
small number of large servers. Also, as you said, you won't get any of the
high availability benefits that it offers if you run multiple copies of
I’d advise keeping read ahead low… or turning it off on SSD. Also, noop IO
scheduler might help you on that disk..
IF Cassandra DOES perform a contiguous read, read ahead won’t be helpful.
It’s essentially obsolete now on SSDs.
On Wed, Sep 24, 2014 at 1:20 PM, Daniel Chia danc...@coursera.org
