27;WhispirStandard') liveRatio is 1.0 (just-counted was 1.0).
calculation took 69ms for 1544 columns
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7264583.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
On Fri, Feb 3, 2012 at 8:46 AM, Jonathan Ellis wrote:
> You should come up with a way to reproduce so we can fix it. :)
This happens when server is idle for a while with not so much data and
then you start a load like 50 write and 50 read requests per sec. We
have 4 CF that we write to and then r
Dne 3.2.2012 17:46, Jonathan Ellis napsal(a):
You should come up with a way to reproduce so we can fix it. :)
it happens after HH delivery when memtable contains lot of deletes
You should come up with a way to reproduce so we can fix it. :)
On Fri, Feb 3, 2012 at 10:31 AM, Mohit Anchlia wrote:
> On Fri, Feb 3, 2012 at 7:32 AM, Jonathan Ellis wrote:
>> It's a warn because it's nonsense for the JVM to report that an column
>> + overhead, takes less space than just the co
On Fri, Feb 3, 2012 at 7:32 AM, Jonathan Ellis wrote:
> It's a warn because it's nonsense for the JVM to report that an column
> + overhead, takes less space than just the column data itself.
>
But is there any action we need to take, or worry about? We trigger
alerts based on WARN and ERROR. But
It's a warn because it's nonsense for the JVM to report that an column
+ overhead, takes less space than just the column data itself.
On Tue, Jan 31, 2012 at 9:41 PM, Mohit Anchlia wrote:
> I guess this is not really a WARN in that case.
>
> On Tue, Jan 31, 2012 at 4:29 PM, aaron morton wrote:
>
I guess this is not really a WARN in that case.
On Tue, Jan 31, 2012 at 4:29 PM, aaron morton wrote:
> The ratio is the ratio of serialised bytes for a memtable to actual JVM
> allocated memory. Using a ratio below 1 would imply the JVM is using less
> bytes to store the memtable in memory than i
Thanks for the explanation.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7242021.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
The ratio is the ratio of serialised bytes for a memtable to actual JVM
allocated memory. Using a ratio below 1 would imply the JVM is using less bytes
to store the memtable in memory than it takes to store it on disk (without
compression).
The ceiling for the ratio is 64.
The ratio is calcu
but a ration of< 1 may occur
for column families with a very high update to insert ratio.
better to ask why minimum ratio is 1.0. What harm can be done with using
< 1.0 ratio?
Dan
-Original Message-
From: Roshan [mailto:codeva...@gmail.com]
Sent: January-30-12 20:04
To: cassandra-u...@incubator.apache.org
Subject: Re: WARN [Memtable] live ratio
Exactly, I am also getting this when server moving idle to high load. May be
Cassandra Experts can help to us.
--
V
Exactly, I am also getting this when server moving idle to high load. May be
Cassandra Experts can help to us.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7238603.html
Sent from the cassandra-u
e in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7238582.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7238582.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
14 matches
Mail list logo
