[
https://issues.apache.org/jira/browse/CASSANDRA-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910912#action_12910912
]
Jonathan Ellis commented on CASSANDRA-1516:
-------------------------------------------
compaction is exposed in compactionmanager, although we could break out the
type of operation more (started in CASSANDRA-1415)
bootstrap is addressed in CASSANDRA-1489
drain we can address by adding progress to CFS.flushWriter and a "drained N out
of M" method to StorageService
for repair you probably need to treat it as "stage 1" (ro compaction) and
"stage 2" (AES + Streaming). i believe AES knows how many hash blocks it has
remaining somewhere.
> 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
>
> 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.
