Yes, it is! I've fixed the problem. I miss the caching property set to
'ALL' to create the columily family.
2013/8/31 Jonathan Haddad
> 9/12 = .75
>
> It's a rate, not a percentage.
>
>
> On Sat, Aug 31, 2013 at 2:21 PM, Sávio Teles
> wrote:
>
>>I'm running one Cassandra node -version 1.2.
9/12 = .75
It's a rate, not a percentage.
On Sat, Aug 31, 2013 at 2:21 PM, Sávio Teles
wrote:
> I'm running one Cassandra node -version 1.2.6- and I *enabled* the *row
> cache* with *1GB*.
> But looking the Cassandra metrics on JConsole, *Row Cache Requests* are
> very *low* a
I'm running one Cassandra node -version 1.2.6- and I *enabled* the *row
cache* with *1GB*.
But looking the Cassandra metrics on JConsole, *Row Cache Requests* are
very *low* after a high number of queries (about 12 requests).
RowCache metrics:
*Capacity: 1GB*
*Entries: 3
*
*HitRate: 0.75
*
*Hits
I have a column family with this conf:
CREATE TABLE geoms (
geom_key text PRIMARY KEY,
part_geom list,
the_geom text
) WITH
bloom_filter_fp_chance=0.01 AND
caching='KEYS_ONLY' AND
comment='' AND
dclocal_read_repair_chance=0.00 AND
gc_grace_seconds=864000 AND
read_repair_c
Do you think that not to run cleanup operation after bootstrapping a node
can affect the bootstrap time of a subsequent node?
I mean, keys not removed can somehow affect a bootstrap operation?
Thanks.
Att.
*Rodrigo Felix de Almeida*
LSBD - Universidade Federal do Ceará
Project Manager
MBA, CSM, C
