https://issues.apache.org/jira/browse/CASSANDRA-1129
On Tue, May 25, 2010 at 3:42 PM, Jonathan Ellis wrote:
> That does look like a bug. Can you create a ticket and upload a
> (preferably small-ish) sstable that illustrates the problem?
>
> On Mon, May 24, 2010 at 12:07 PM, Ran Tavory wrote:
That does look like a bug. Can you create a ticket and upload a
(preferably small-ish) sstable that illustrates the problem?
On Mon, May 24, 2010 at 12:07 PM, Ran Tavory wrote:
> I'd like to have 100% keys cached. Sorry if my example of Super2 wasn't
> correct, but I do think there's a problem.
I'd like to have 100% keys cached. Sorry if my example of Super2 wasn't
correct, but I do think there's a problem. Here's with my own data:
When using actual numbers (in this case for RowsCached) it works as
expected, however when specifying KeysCached="100%" I get only 1.
If you really want a cache capacity of 0 then you need to use 0
explicitly, otherwise the % versions will give you at least 1.
On Mon, May 24, 2010 at 12:34 AM, Ran Tavory wrote:
> I've noticed that when defining KeysCached="50%" (or KeysCached="100%" and I
> didn't test other values with %) then
50% of 0 will be rounded up to 1.
-Original Message-
From: "Ran Tavory"
Sent: Monday, May 24, 2010 12:34am
To: user@cassandra.apache.org
Subject: Key cache capacity: 1 when using KeysCached="50%"
I've noticed that when defining KeysCached="50%" (or
I've noticed that when defining KeysCached="50%" (or KeysCached="100%" and I
didn't test other values with %) then cfstats reports Key cache capacity: 1
This looks weird... is this expected? (version 0.6.1)
For example, in the default configuration:
Keyspace: Keyspace1
