Database Reference
In-Depth Information
tionStage
0
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,292
StatusLogger.java (line 65)
StreamStage
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,292
StatusLogger.java (line 65)
MemtablePostFlush-
er
0
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,292
StatusLogger.java (line 65)
FlushWriter
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,292
StatusLogger.java (line 65)
Mis-
cStage
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,292
StatusLogger.java (line 65)
InternalRespon-
seStage
0
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,293
StatusLogger.java (line 65)
HintedHan-
doff
1
8
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,293
StatusLogger.java (line 70)
CompactionMan-
ager
0
0
INFO [ScheduledTasks:1] 2012-07-09 20:48:57,293
StatusLogger.java (line 82)
MessagingService
n/
a
0,0
When you see messages being dropped, as in the first two lines of the listing,
that's a sign that your system is under stress. Depending on your application re-
quirements, some level of dropped messages may be acceptable. But regardless
of whether or not your application can tolerate running in a degraded state, the
overall health of your cluster (or at the very least this node) is in question.
