cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7043) CommitLogArchiver thread pool name inconsistent with others
Date Tue, 15 Apr 2014 22:09:16 GMT
Chris Lohfink created CASSANDRA-7043:
----------------------------------------

             Summary: CommitLogArchiver thread pool name inconsistent with others
                 Key: CASSANDRA-7043
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7043
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Chris Lohfink
            Priority: Trivial
         Attachments: namechange.diff

Pretty trivial... The names of all ThreadPoolExecutors are in CamelCase except the CommitLogArchiver
as commitlog_archiver.  This shows up a little more obvious in tpstats output:

{code}
nodetool tpstats

Pool Name                    Active   Pending      Completed   Blocked  
ReadStage                         0         0         113702         0               
RequestResponseStage              0         0              0         0               
...
PendingRangeCalculator            0         0              1         0                 
commitlog_archiver                0         0              0         0                 
InternalResponseStage             0         0              0         0                 
HintedHandoff                     0         0              0         0                 
{code}

Seems minor enough to update this to be CommitLogArchiver but it may mean changes in any monitoring
applications (although I don't think this particular pool has had much runtime or monitoring
needs).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message