incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: 1.2.3 and 1.2.4 memory usage growth on idle cluster
Date Sun, 28 Apr 2013 17:51:58 GMT
> INFO 11:10:56,273 GC for ParNew: 1039 ms for 1 collections, 6631277912 used; max is 10630070272
It depends on the settings. It looks like you are using non default JVM settings. 

It'd recommend restoring the default JVM settings as a start. 

CHeers

-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 25/04/2013, at 9:30 PM, Igor <igor@4friends.od.ua> wrote:

> Hello
> 
> Does  anybody seen memory problems on idle cluster?
> I have 8-node ring with cassandra 1.2.3 which never been used and stay idle for several
weeks. Yesterday when I decided to upgrade it to 1.2.4 I found lot of messages like
> 
> INFO 11:10:56,273 GC for ParNew: 1039 ms for 1 collections, 6631277912 used; max is 10630070272
> INFO 11:10:56,273 Pool Name                    Active   Pending Blocked
> INFO 11:10:56,275 ReadStage                         0 0         0
> INFO 11:10:56,276 RequestResponseStage              0 0         0
> INFO 11:10:56,276 ReadRepairStage                   0 0         0
> INFO 11:10:56,277 MutationStage                     0 0         0
> INFO 11:10:56,277 ReplicateOnWriteStage             0 0         0
> INFO 11:10:56,278 GossipStage                       0 0         0
> INFO 11:10:56,278 AntiEntropyStage                  0 0         0
> INFO 11:10:56,278 MigrationStage                    0 0         0
> INFO 11:10:56,279 MemtablePostFlusher               0 0         0
> INFO 11:10:56,279 FlushWriter                       0 0         0
> INFO 11:10:56,280 MiscStage                         0 0         0
> INFO 11:10:56,280 commitlog_archiver                0 0         0
> INFO 11:10:56,280 InternalResponseStage             0 0         0
> INFO 11:10:56,281 HintedHandoff                     0 0         0
> INFO 11:10:56,281 CompactionManager                 0         0
> INFO 11:10:56,281 MessagingService                n/a       0,0
> INFO 11:10:56,281 Cache Type Size                 Capacity               KeysToSave
>                                                        Provider
> INFO 11:10:56,281 KeyCache 7368                104857600                      all
> 
> INFO 11:10:56,281 RowCache 0                        0                      all
>             org.apache.cassandra.cache.SerializingCacheProvider
> INFO 11:10:56,281 ColumnFamily                Memtable ops,data
> INFO 11:10:56,281 system.local                             4,52
> INFO 11:10:56,281 system.peers                          30,6093
> INFO 11:10:56,282 system.batchlog                           0,0
> INFO 11:10:56,282 system.NodeIdInfo                         0,0
> INFO 11:10:56,282 system.LocationInfo                       0,0
> INFO 11:10:56,282 system.Schema                             0,0
> INFO 11:10:56,282 system.Migrations                         0,0
> INFO 11:10:56,282 system.schema_keyspaces                   0,0
> INFO 11:10:56,282 system.schema_columns                     0,0
> INFO 11:10:56,282 system.schema_columnfamilies                 0,0
> INFO 11:10:56,282 system.IndexInfo                          0,0
> INFO 11:10:56,282 system.range_xfers                        0,0
> INFO 11:10:56,282 system.peer_events                        0,0
> INFO 11:10:56,283 system.hints                              0,0
> INFO 11:10:56,283 system.HintsColumnFamily                  0,0
> INFO 11:10:56,283 system_auth.users                         0,0
> INFO 11:10:56,283 system_traces.sessions                    0,0
> INFO 11:10:56,283 system_traces.events                      0,0
> INFO 11:11:21,205 GC for ParNew: 1035 ms for 1 collections, 6633037168 used; max is 10630070272
> 
> So you can see - there is no any activity. And what I can see from the java heap graph
- it constantly grow. I plan to use this ring in prod, but this strange behaviour confuses
me.
> 


Mime
View raw message