all features(Super Columns, caching, pooling, etc) of Cassandra 1.X.
>> Right now i come to know that following client exists:
>>
>> 1) Hector(Java)
>> 2) Thrift (Java)
>> 3) Kundera (Java)
>>
>>
(1024,1867)=1867MB or in other
>> words 1/4 of RAM.
>>
>> In http://www.datastax.com/docs/1.0/operations/tuning it says: "Cassandra's
>> default configuration opens the JVM with a heap size of 1/4 of the available
>> system memory (or a minimum 1GB and maximu
hs since the
> upgrade, but they show promising results compared to the slope of the same
> graph before the upgrade to 1.1.2
>
> So my advice is give 1.1.2 a shot - just be mindful of
> https://issues.apache.org/jira/browse/CASSANDRA-4411
>
>
> On 2012-07-26, at 2:18 A
lidation
> 3. The HEAP usage within the JVM is stable over time
> 4. The RESident size of the process appears also stable over time
>
> Point #4 above is still pending as I only have 3 day graphs since the
> upgrade, but they show promising results compared to the slo
ap
>
> On Wed, Jul 25, 2012 at 1:21 AM, Thomas Spengler <
> thomas.speng...@toptarif.de> wrote:
>
>> No one has any idea?
>>
>> we tryed
>>
>> update to 1.1.2
>> DiskAccessMode standard, indexAccessMode standard
>> row_cache_siz
Is there any way to limit the off heap memory usage for cassandra 1.1.X
Thx
--
Thomas Spengler
, Thomas Spengler wrote:
> Hi @all,
>
> since our upgrade form cassandra 1.0.3 to 1.1.0 the virtual memory usage
> of the cassandra-nodes explodes
>
> our setup is:
> * 5 - centos 5.8 nodes
> * each 4 CPU's and 8 GB RAM
> * each node holds about 100 GB on
essMode is standard
The memory usage grows upto the whole memory is used.
Just for information, as we had cassandra 1.0.3, we used
* DiskAccessMode is standard, indexAccessMode is mmap
* and the ram-usage was ~4GB
can anyone help?
With Regards
--
Thomas Spengler
