Ok, thanks Matija.




On Tue, Feb 21, 2017, at 11:43 AM, Matija Gobec wrote:

> They appear for each repair run and disappear when repair run
> finishes.
> 

> On Tue, Feb 21, 2017 at 11:14 AM, Vincent Rischmann
> <m...@vrischmann.me> wrote:
>> __

>> Hi,

>> 

>> I upgraded to Cassandra 2.2.8 and noticed something weird in nodetool
>> tpstats:
>> 

>> Pool Name                    Active   Pending      Completed
>> Blocked  All time blocked
>> MutationStage                     0         0      116265693
>> 0                 0
>> ReadStage                         1         0       56132474
>> 0                 0
>> RequestResponseStage              0         0      163640931
>> 0                 0
>> ReadRepairStage                   0         0        3152856
>> 0                 0
>> CounterMutationStage              0         0         630690
>> 0                 0
>> Repair#26                         1         4              1
>> 0                 0
>> Repair#48                         1         2              3
>> 0                 0
>> HintedHandoff                     1         1           1198
>> 0                 0
>> MiscStage                         0         0              0
>> 0                 0
>> CompactionExecutor                0         0         111438
>> 0                 0
>> Repair#45                         1         4              1
>> 0                 0
>> MemtableReclaimMemory             0         0           3399
>> 0                 0
>> Repair#30                         1         4              1
>> 0                 0
>> PendingRangeCalculator            0         0             37
>> 0                 0
>> Repair#61                         1         4              1
>> 0
>> 

>> There are multiples "pools" named Repair#<repair number> which
>> weren't there with Cassandra 2.1.16. These appear in the JMX
>> metrics too.
>> 

>> Do they go away eventually ? because this is making the tpstats
>> output harder to read in my opinion

Reply via email to