Java cassandra 2.1线程cpu用户时间100

我使用几个进程通过tcp编写cassandra。一开始很好。内存达到50%后，我的进程有很多超时。此时一个cassandra线程的cpu用户时间长达100%，system.log如下：

INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,996 StatusLogger.java:115 - RRD2.AVE_WK                         1906,2098
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,997 StatusLogger.java:115 - RRD2.RRA                                  0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,997 StatusLogger.java:115 - system.schema_triggers                    0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,997 StatusLogger.java:115 - system.local                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,997 StatusLogger.java:115 - system.peers                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,997 StatusLogger.java:115 - system.batchlog                           0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.NodeIdInfo                         0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.compactions_in_progress                 0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.schema_usertypes                   0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.schema_keyspaces                   0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.compaction_history                 0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,998 StatusLogger.java:115 - system.paxos                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,999 StatusLogger.java:115 - system.schema_columns                     0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,999 StatusLogger.java:115 - system.schema_columnfamilies                 0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,999 StatusLogger.java:115 - system.IndexInfo                          0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,999 StatusLogger.java:115 - system.range_xfers                        0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:43,999 StatusLogger.java:115 - system.peer_events                        0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:44,000 StatusLogger.java:115 - system.hints                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:44,000 StatusLogger.java:115 - system.sstable_activity                   0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:44,000 StatusLogger.java:115 - system_traces.sessions                    0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:01:44,000 StatusLogger.java:115 - system_traces.events                      0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:06,068 GCInspector.java:116 - GC for ConcurrentMarkSweep: 21284 ms for 1 collections, 4226524688 used; max is 4242538496
INFO  [ScheduledTasks:1] 2014-05-09 15:02:06,069 StatusLogger.java:51 - Pool Name                    Active   Pending      Completed   Blocked  All Time Blocked
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,897 StatusLogger.java:66 - CounterMutationStage              0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,898 StatusLogger.java:66 - ReadStage                         0         0            106         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,898 StatusLogger.java:66 - RequestResponseStage              0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,899 StatusLogger.java:66 - ReadRepairStage                   0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,899 StatusLogger.java:66 - MutationStage                    32        92          20620         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,900 StatusLogger.java:66 - GossipStage                       0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,900 StatusLogger.java:66 - AntiEntropyStage                  0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,901 StatusLogger.java:66 - MigrationStage                    0         0              8         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,901 StatusLogger.java:66 - MiscStage                         0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,902 StatusLogger.java:66 - MemtableFlushWriter               2         8             23         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,902 StatusLogger.java:66 - PendingRangeCalculator            0         0              1         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,903 StatusLogger.java:66 - MemtablePostFlush                 1        46             69         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,903 StatusLogger.java:66 - commitlog_archiver                0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,904 StatusLogger.java:66 - InternalResponseStage             0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,904 StatusLogger.java:66 - HintedHandoff                     0         0              0         0                 0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,905 StatusLogger.java:75 - CompactionManager                 0         0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,905 StatusLogger.java:87 - MessagingService                n/a       0/0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,905 StatusLogger.java:97 - Cache Type                     Size                 Capacity               KeysToSave
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,905 StatusLogger.java:99 - KeyCache                       2208                104857600                      all
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,905 StatusLogger.java:105 - RowCache                          0                        0                      all
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:112 - ColumnFamily                Memtable ops,data
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:115 - RRD2.DS                                   0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:115 - RRD2.CDP                       2226732,476355
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:115 - RRD2.AVE_MO                         3040,3722
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:115 - RRD2.PDP                        923845,604642
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,906 StatusLogger.java:115 - RRD2.AVE_HR                   943064,83811099
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,907 StatusLogger.java:115 - RRD2.AVE_YR                           120,164
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,907 StatusLogger.java:115 - RRD2.AVE_WK                         3040,3722
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,907 StatusLogger.java:115 - RRD2.RRA                                  0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,916 StatusLogger.java:115 - system.schema_triggers                    0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,916 StatusLogger.java:115 - system.local                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,916 StatusLogger.java:115 - system.peers                              0,0
INFO  [ScheduledTasks:1] 2014-05-09 15:02:21,936 StatusLogger.java:115 - system.batchlog                           0,0
WARN  [PERIODIC-COMMIT-LOG-SYNCER] 2014-05-09 15:08:56,334 AbstractCommitLogService.java:105 - Out of 11 commit log syncs over the past 321s with average duration of 26478.00ms, 7 have exceeded the configured commit interval by an average of 31464.57ms

---

有人知道发生了什么吗？

这里的这一行表示您正在重载节点，使其运行我们的java堆空间：

INFO  [ScheduledTasks:1] 2014-05-09 15:02:06,068 GCInspector.java:116 - GC for ConcurrentMarkSweep: 21284 ms for 1 collections, 4226524688 used; max is 4242538496

---

您可能需要调回一些缓存或memtable之类的东西。如果您进行堆转储，您可以找出是什么在使用所有内存。

下面是为什么会看到StatusLogger条目。状态记录器在卡桑德拉的特定“压力”时期转储一些关键指标。正如Zanson指出的，由于垃圾收集的运行，您特别看到了这一点

默认情况下，在\u ms中有一个名为

gc\u log\u threshold\u的配置条目，默认为200ms（可在配置中调整），任何>200ms的垃圾收集都将记录您看到的状态记录器条目

此外，还有另一个名为
gc\u warn\u threshold\u in_ms
的配置条目，如果垃圾收集运行时间>1000ms（默认情况下，也可调整），它将在
warn
日志级别记录这些条目，而不是
INFO
。
warn[PERIODIC-COMMIT-log-SYNCER]2014-05-09 15:08:56334 AbstractCommitLogService.java:105-在过去321年间的11次提交日志同步（平均持续时间为26478.00ms）中，有7次超过了配置的提交间隔，平均时间为31464.57ms
。不知道cassandra是什么，但超过配置的提交间隔32秒对我来说似乎是可疑的。这不是一个在中定义的主题编程问题，它是关于NoSQL数据库管理的，因此属于上。@Cupcake:我很高兴它在这里，其他堆栈站点也不总是被索引。