You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2010/10/07 00:12:31 UTC
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918706#action_12918706 ]
Nick Bailey commented on CASSANDRA-1586:
----------------------------------------
Isn't this the same as CASSANDRA-1516
> Explicitly expose ongoing per-node compaction tasks and est. % done
> -------------------------------------------------------------------
>
> Key: CASSANDRA-1586
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1586
> Project: Cassandra
> Issue Type: Wish
> Components: Core
> Reporter: paul cannon
> Priority: Minor
>
> CompactionManagerMBean exports the number of bytes compacted and the total number to be compacted during a given job, but I don't believe it says what sort of compaction it's doing (anti-compaction, validation compaction, index build, or an SSTable build after receiving an incoming streamed file).
> Is it possible to have multiple threads going in the compaction manager? (It doesn't look like it, but I don't see any explicit maximumPoolSize setting.) If so, cassandra should also expose all ongoing compaction tasks and progress for each individually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.