You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/12/23 00:23:29 UTC
[jira] Commented: (CASSANDRA-599) The pending tasks listed for the
compaction pool is confusing
[ https://issues.apache.org/jira/browse/CASSANDRA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793841#action_12793841 ]
Jonathan Ellis commented on CASSANDRA-599:
------------------------------------------
05
make estimation of pendingtasks for CompactionManager sane
04
move initial check for compaction to after log replay
03
expose cf count, disk space to JMX
02
abstract DebuggableThreadPoolExecutor from JMX stats
01
clean up compactions api and move into CompactionManager
> The pending tasks listed for the compaction pool is confusing
> -------------------------------------------------------------
>
> Key: CASSANDRA-599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-599
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: RHEL 4
> Reporter: Tim Freeman
> Assignee: Jonathan Ellis
> Priority: Trivial
> Fix For: 0.9
>
> Attachments: 0001-clean-up-compactions-api-and-move-into-CompactionManag.txt, 0002-abstract-DTPE-from-JMXETPE.txt, 0003-expose-cf-count-disk-space-to-JMX.txt, 0004-move-initial-check-for-compaction-to-after-log-replay.txt, 0005-make-estimation-of-pendingtasks-for-CompactionManager-.txt
>
>
> Using the build dated 29 Nov 09, the output from "nodeprobe tpstats" is confusing. The following observations were made with an idle server that was compacting to clean up after some writes that were done in the past. The number of pending tasks for COMPACTION-POOL starts at 1673, and after doing some work the number of pending tasks has increased to 1675. I'd prefer that the amount of pending work reported by tpstats decreases as work is done.
> > sh nodeprobe.sh tpstats
> Pool Name Active Pending Completed
> FILEUTILS-DELETE-POOL 0 0 872
> MESSAGING-SERVICE-POOL 0 0 0
> STREAM-STAGE 0 0 0
> RESPONSE-STAGE 0 0 662309
> ROW-READ-STAGE 0 0 662309
> LB-OPERATIONS 0 0 0
> COMMITLOG 1 0 1189659
> MESSAGE-DESERIALIZER-POOL 0 0 0
> GMFD 0 0 0
> LB-TARGET 0 0 0
> CONSISTENCY-MANAGER 0 0 0
> ROW-MUTATION-STAGE 0 0 1101916
> MESSAGE-STREAMING-POOL 0 0 0
> LOAD-BALANCER-STAGE 0 0 0
> FLUSH-SORTER-POOL 0 0 1723
> MEMTABLE-POST-FLUSHER 0 0 1723
> COMPACTION-POOL 1 1673 136
> FLUSH-WRITER-POOL 0 0 1723
> HINTED-HANDOFF-POOL 0 0 20
> > sh nodeprobe.sh tpstats
> Pool Name Active Pending Completed
> FILEUTILS-DELETE-POOL 0 0 872
> MESSAGING-SERVICE-POOL 0 0 0
> STREAM-STAGE 0 0 0
> RESPONSE-STAGE 0 0 662309
> ROW-READ-STAGE 0 0 662309
> LB-OPERATIONS 0 0 0
> COMMITLOG 1 0 1191173
> MESSAGE-DESERIALIZER-POOL 0 0 0
> GMFD 0 0 0
> LB-TARGET 0 0 0
> CONSISTENCY-MANAGER 0 0 0
> ROW-MUTATION-STAGE 0 0 1101916
> MESSAGE-STREAMING-POOL 0 0 0
> LOAD-BALANCER-STAGE 0 0 0
> FLUSH-SORTER-POOL 0 0 1723
> MEMTABLE-POST-FLUSHER 0 0 1723
> COMPACTION-POOL 1 1675 139
> FLUSH-WRITER-POOL 0 0 1723
> HINTED-HANDOFF-POOL 0 0 20
> (^[[01;32mroot@localhost^[[00m)^[[01;34m~/rackspace-stuff/cassandra-0.5-pre^[[00m>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.