You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2010/10/07 00:08:32 UTC
[jira] Created: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
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.
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920258#action_12920258 ]
Jonathan Ellis commented on CASSANDRA-1586:
-------------------------------------------
patch exposes compaction type in mbean. also changes AntiCompaction type to Cleanup, since that is the only thing it is used for now, and removes submitAntiCompaction method.
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Updated: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-1586:
-----------------------------------
Issue Type: Sub-task (was: Wish)
Parent: 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: Sub-task
> 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.
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920351#action_12920351 ]
Gary Dusbabek commented on CASSANDRA-1586:
------------------------------------------
+1
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918708#action_12918708 ]
paul cannon commented on CASSANDRA-1586:
----------------------------------------
yes. i'm making subtasks, per request
> 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: Sub-task
> 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.
[jira] Updated: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1586:
--------------------------------------
Component/s: (was: Core)
Tools
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Commented: (CASSANDRA-1586) Explicitly expose ongoing
per-node compaction tasks and est. % done
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920949#action_12920949 ]
Hudson commented on CASSANDRA-1586:
-----------------------------------
Integrated in Cassandra #565 (See [https://hudson.apache.org/hudson/job/Cassandra/565/])
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Updated: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1586:
--------------------------------------
Attachment: 1586.txt
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Updated: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1586:
--------------------------------------
Attachment: (was: 1586.txt)
> 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: Sub-task
> Components: Tools
> Reporter: paul cannon
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.
[jira] Updated: (CASSANDRA-1586) Explicitly expose ongoing per-node
compaction tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1586:
--------------------------------------
Attachment: 1586.txt
> 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: Sub-task
> Components: Core
> Reporter: paul cannon
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1586.txt
>
>
> 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.