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 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, 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 data > > * each jvm's uses 2GB Ram > > * DiskAccessMode is standard, indexAccessMode 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 > Chief Technology Officer > ------------------------------------------------------------------------ > > TopTarif Internet GmbH, Pappelallee 78-79, D-10437 Berlin > Tel.: (030) 2000912 0 | Fax: (030) 2000912 100 > thomas.speng...@toptarif.de | www.toptarif.de > > Amtsgericht Charlottenburg, HRB 113287 B > Geschäftsführer: Dr. Rainer Brosch, Dr. Carolin Gabor > ------------------------------------------------------------------------- > > > -- Tyler Hobbs DataStax <http://datastax.com/>
