On Wed, Apr 4, 2012 at 8:04 AM, aaron morton wrote:
> It depends on the workload.
>
> Increase the cache size until you see the hit rate decrease, or see it
> create memory pressure. Watch the logs for messages that the caches have
> been decreased.
>
> Take a look at the Recent Read Latency for t
On Tue, Apr 3, 2012 at 11:49 AM, aaron morton wrote:
> Take a look at the key cache hit rate in nodetool cfstats.
>
> One approach is to increase the cache size until you do not see a matching
> increase in the hit rate.
>
Thanks Aaron, what do you think will be the ideal cache hit ratio where w
Hi guys,
We are calculating key cache size right now. There is this column family
with ~ 100 million columns and right now we have the cache size set at 2
million.
I suspect that the active data we got is not all fitting in the 2 million
cache size and we at times are getting query execution time
On Wed, Mar 21, 2012 at 4:45 AM, aaron morton wrote:
> no, describe cluster is a feature of the CLI.
>
>
How will you recommend doing schema level health checks (consistency) for
Cassandra within the cluster?
cheers,
Shoaib
On Tue, Mar 20, 2012 at 4:18 AM, aaron morton wrote:
> There is a server side check to ensure that all available nodes share the
> same schema version.
>
>
Is that checked using "describe cluster" ??
cheers,
Shoaib
Hi guys,
While creating schema on our cluster today I didn't get any errors even
when some of the hosts in the cluster were unreachable (not the ones in the
same data centre but in another region). cli kept on showing all nodes
agreeing where all nodes were agreeing.
Now after this when I did "de
