I have seen this behavour when Commitlog files got deleted (or permissions were set to read only).
MemtablePostFlusher is the stage that marks the Commitlog as flushed. When they fail it usually means there is something wrong with the commitlog files. Check your logfiles for any commitlog related errors. regards, Christian On Tue, Jul 15, 2014 at 7:03 PM, Kais Ahmed <k...@neteck-fr.com> wrote: > Hi all, > > I have a small cluster (2 nodes RF 2) running with C* 2.0.6 on I2 Extra > Large (AWS) with SSD disk, > the nodetool tpstats shows many MemtablePostFlusher pending and > FlushWriter All time blocked. > > The two nodes have the default configuration. All CF use size-tiered > compaction strategy. > > There are 10 times more reads than writes (1300 reads/s and 150 writes/s). > > > ubuntu@node1 :~$ nodetool tpstats > Pool Name Active Pending Completed Blocked > All time blocked > MemtablePostFlusher 1 1158 159590 > 0 0 > FlushWriter 0 0 11568 > 0 1031 > > ubuntu@node1:~$ nodetool compactionstats > pending tasks: 90 > Active compaction remaining time : n/a > > > ubuntu@node2:~$ nodetool tpstats > Pool Name Active Pending Completed Blocked > All time blocked > MemtablePostFlusher 1 1020 50987 > 0 0 > FlushWriter 0 0 6672 > 0 948 > > > ubuntu@node2:~$ nodetool compactionstats > pending tasks: 89 > Active compaction remaining time : n/a > > I think there is something wrong, thank you for your help. > >
