we have monitoring of std *nix stuff via zabbix
and cassandra, as all other java via mbeans and zabbix
Best
Tom
Original Message
Subject: Re: virtual memory of all cassandra-nodes is growing extremly
since Cassandra 1.1.0
Date: Wed, 1 Aug 2012 14:43:17 -0500
From: Greg Fausak
All our servers (cassandra and otherwise) get monitored with nagios + get many
basic metrics graphed by pnp4nagios. This covers a large chunk of a box's
health, as well as cassandra basics (specifically the pending tasks, JVM heap
state). IMO it's not possible to clearly debug a cassandra iss
Mina,
Thanks for that post. Very interesting :-)
What sort of things are you graphing? Standard *nux stuff
(mem/cpu/etc)? Or do you
have some hooks in to the C* process (I saw somoething about port 1414
in the .yaml file).
Best,
-g
On Thu, Jul 26, 2012 at 9:27 AM, Mina Naguib
wrote:
>
> H
Just for information
we are running on 1.1.2
JNA or not, had no difference
Manually call full gc, had no difference
but
in my case
the reduction of
commitlog_total_space_in_mb to 2048 (from default 4096)
makes the difference.
On 07/26/2012 04:27 PM, Mina Naguib wrote:
>
> Hi Thomas
>
> On
Hi Thomas
On a modern 64bit server, I recommend you pay little attention to the virtual
size. It's made up of almost everything within the process's address space,
including on-disk files mmap()ed in for zero-copy access. It's not
unreasonable for a machine with N amount RAM to have a proces
I saw this.
All works fine upto version 1.1.0
the 0.8.x takes 5GB of memory of an 8GB machine
the 1.0.x takes between 6 and 7 GB on a 8GB machine
and
the 1.1.0 takes all
and it is a problem
for me it is no solution to wait of the OOM-Killer from the linux kernel
and restart the cassandraprocess
Are you actually seeing any problems from this? High virtual memory usage
on its own really doesn't mean anything. See
http://wiki.apache.org/cassandra/FAQ#mmap
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
No one has any idea?
we tryed
update to 1.1.2
DiskAccessMode standard, indexAccessMode standard
row_cache_size_in_mb: 0
key_cache_size_in_mb: 0
Our next try will to change
SerializingCacheProvider to ConcurrentLinkedHashCacheProvider
any other proposals are welcom
On 07/04/2012 02:13 PM, Tho
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 data
* each jvm's uses 2GB Ram
* DiskAccessMode is standard, indexAccessMode is stan
