You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/04/22 18:32:15 UTC
[jira] [Resolved] (CASSANDRA-7043) CommitLogArchiver thread pool
name inconsistent with others
[ https://issues.apache.org/jira/browse/CASSANDRA-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-7043.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 2.1 beta2
Reviewer: Brandon Williams
Assignee: Chris Lohfink
Committed.
> 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
> Assignee: Chris Lohfink
> Priority: Trivial
> Fix For: 2.1 beta2
>
> 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)