On Thu, Nov 14, 2013 at 10:05 AM, J. Ryan Earl wrote:
> * Cassandra 2.0.2 has a lot of improvements, consider upgrading. We
> noticed improved heap usage compared to 2.0.2
>
https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/
And especially if you're using Level Compacti
First off, I'm curious what hardware (system specs) you're running this on?
Secondly, here are some observations:
* You're not running the newest JDK7, I can tell by your stack-size.
Consider getting the newest.
* Cassandra 2.0.2 has a lot of improvements, consider upgrading. We
noticed improve
Hi,
On 11/12/2013 05:29 AM, Aaron Morton wrote:
>>> Are you doing large slices or do could you have a lot of tombstones
>>> on the rows ?
>> don't really know - how can I monitor that?
> For tombstones, do you do a lot of deletes ?
> Also in v2.0.2 cfstats has this
>
> Average live cells per sli
>> Are you doing large slices or do could you have a lot of tombstones on the
>> rows ?
> don't really know - how can I monitor that?
For tombstones, do you do a lot of deletes ?
Also in v2.0.2 cfstats has this
Average live cells per slice (last five minutes): 0.0
Hi,
On 11/07/2013 05:18 AM, Aaron Morton wrote:
>> Class Name
>>| Shallow Heap | Retained Heap
>> --
On 11/06/2013 11:18 PM, Aaron Morton wrote:
The default row cache is of the JVM heap, have you changed to the
ConcurrentLinkedHashCacheProvider ?
ConcurrentLinkedHashCacheProvider was removed in 2.0.x.
> Class Name
> | Shallow Heap | Retained Heap
> ---
>
Both caches involve several objects per entry (What do we want? Packed
objects. When do we want them? Now!). The "size" is an estimate of the
off heap values only and not the total size nor number of entries.
An acceptable size will depend on your data and access patterns. In one
case we h
We have the same problem.
2013/11/5 Jiri Horky
> Hi there,
>
> we are seeing extensive memory allocation leading to quite long and
> frequent GC pauses when using row cache. This is on cassandra 2.0.0
> cluster with JNA 4.0 library with following settings:
>
> key_cache_size_in_mb: 300
> key_ca
