cassandra - CPU usage goes high when read -
i using cassandra 1.2.5, have 4 nodes in cluster. each node m1.large system memory 8gb. read more. have 50,000 rows in column family. when ever try read data column family, every time either node3 or node4 cpu usage going high. have given logs below this.
can make compaction strategy leveledcompactionstrategy , sstable_size_in_mb 10 problem. help?
is there other solution this?
logs:
info [scheduledtasks:1] 2013-07-25 12:59:04,660 statuslogger.java (line 95) cache type size capacity keystosave provider info [scheduledtasks:1] 2013-07-25 12:59:04,660 statuslogger.java (line 96) keycache 18523284 52428800 info [scheduledtasks:1] 2013-07-25 12:59:04,661 statuslogger.java (line 102) rowcache 0 1073741824 org.apache.cassandra.cache.serializingcacheprovider info [scheduledtasks:1] 2013-07-25 12:59:04,661 statuslogger.java (line 109) columnfamily memtable ops,data info [scheduledtasks:1] 2013-07-25 12:59:04,661 statuslogger.java (line 112) system.local 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,661 statuslogger.java (line 112) system.peers 60,8040 info [scheduledtasks:1] 2013-07-25 12:59:04,662 statuslogger.java (line 112) system.batchlog 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,671 statuslogger.java (line 112) system.nodeidinfo 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,671 statuslogger.java (line 112) system.locationinfo 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,671 statuslogger.java (line 112) system.schema 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,671 statuslogger.java (line 112) system.migrations 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,672 statuslogger.java (line 112) system.schema_keyspaces 8,251 info [scheduledtasks:1] 2013-07-25 12:59:04,672 statuslogger.java (line 112) system.schema_columns 332,21903 info [scheduledtasks:1] 2013-07-25 12:59:04,672 statuslogger.java (line 112) system.schema_columnfamilies 352,21775 info [scheduledtasks:1] 2013-07-25 12:59:04,672 statuslogger.java (line 112) system.indexinfo 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,672 statuslogger.java (line 112) system.range_xfers 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,673 statuslogger.java (line 112) system.peer_events 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,673 statuslogger.java (line 112) system.hints 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,673 statuslogger.java (line 112) system.hintscolumnfamily 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,673 statuslogger.java (line 112) gen_gen.feedserver_dependentfeeds 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,673 statuslogger.java (line 112) gen_gen.feedserver_componentname 18648,1048576 info [scheduledtasks:1] 2013-07-25 12:59:04,674 statuslogger.java (line 112) gen_gen.feedserver_feedscheduler 128952,2097152 info [scheduledtasks:1] 2013-07-25 12:59:04,739 statuslogger.java (line 112) gen_gen.feedserver_feedtype 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,739 statuslogger.java (line 112) gen_gen.feedserver_itemdef 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,739 statuslogger.java (line 112) gen_gen.feedserver_feed 66629,2097152 info [scheduledtasks:1] 2013-07-25 12:59:04,740 statuslogger.java (line 112) system_auth.users 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,740 statuslogger.java (line 112) opscenter.events 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,740 statuslogger.java (line 112) opscenter.rollups60 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,740 statuslogger.java (line 112) opscenter.settings 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,740 statuslogger.java (line 112) opscenter.pdps 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,741 statuslogger.java (line 112) opscenter.rollups86400 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,741 statuslogger.java (line 112) opscenter.events_timeline 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,741 statuslogger.java (line 112) opscenter.rollups300 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,741 statuslogger.java (line 112) opscenter.rollups7200 0,0 info [scheduledtasks:1] 2013-07-25 12:59:04,741 statuslogger.java (line 112) system_traces.sessions 0,0
if you're seeing memory pressure during reads, you're reading many rows @ once. tracing request can give more visibility what's going on: http://www.datastax.com/dev/blog/tracing-in-cassandra-1-2
Comments
Post a Comment