[jira] Resolved: (CASSANDRA-1516) Explicitly expose ongoing per-node tasks (like compactions, repair, etc) and est. % done

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1516.
---------------------------------------

    Resolution: Fixed

> Explicitly expose ongoing per-node tasks (like compactions, repair, etc) and est. % done
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1516
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1516
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: paul cannon
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 0001-Mbean-for-tracking-progress-on-a-pending-drain.patch
>
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> so major compaction, read-only compaction, repair, drain, and bootstrap are the on-node tasks I'm pretty sure make sense to be exposed in this way.  snapshotting might make sense too.
> some of these can be "detected" using heuristics on the number of tasks alive in different stages, but it would be preferable if it could be made more clear.
> the interface should allow multiple tasks and respective percentages to be ongoing at the same time, especially since some tasks (like repair) implicitly kick off other sub-tasks (compaction) and both of them would normally show up at the same time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.