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:26:31 UTC
[jira] Created: (CASSANDRA-1587) Explicitly expose ongoing per-node
repair tasks and est. % done
Explicitly expose ongoing per-node repair tasks and est. % done
---------------------------------------------------------------
Key: CASSANDRA-1587
URL: https://issues.apache.org/jira/browse/CASSANDRA-1587
Project: Cassandra
Issue Type: Wish
Components: Core
Reporter: paul cannon
Priority: Minor
from my unfamiliar review of the code, it looks like this should involve exposing the number and progress of AntiEntropyService Validators. But I could be wrong.
If a repair task involves a sub-task like compaction (see #1586), then ideally both would be visible 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.
[jira] Resolved: (CASSANDRA-1587) Explicitly expose ongoing
per-node repair tasks and est. % done
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1587.
---------------------------------------
Resolution: Not A Problem
i think we are good for 0.7.0?
we have progress of current validator on CompactionManager (CASSANDRA-1586 shows op type on CM now), and we have differencers pending on o.a.c.internal.Antientropy.
what we don't have is a breakdown of how many pending tasks on CompactionManager are validators instead of minor compactions, but for "good enough" i think we can ignore these.
we also don't have current differencer progress but i believe these are relatively fast.
> Explicitly expose ongoing per-node repair tasks and est. % done
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1587
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: paul cannon
> Priority: Minor
>
> from my unfamiliar review of the code, it looks like this should involve exposing the number and progress of AntiEntropyService Validators. But I could be wrong.
> If a repair task involves a sub-task like compaction (see #1586), then ideally both would be visible 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.
[jira] Commented: (CASSANDRA-1587) Explicitly expose ongoing
per-node repair tasks and est. % done
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918765#action_12918765 ]
paul cannon commented on CASSANDRA-1587:
----------------------------------------
I believe it would be sufficient only to show the status of local Validators.
> Explicitly expose ongoing per-node repair tasks and est. % done
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1587
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: paul cannon
> Priority: Minor
>
> from my unfamiliar review of the code, it looks like this should involve exposing the number and progress of AntiEntropyService Validators. But I could be wrong.
> If a repair task involves a sub-task like compaction (see #1586), then ideally both would be visible 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.
[jira] Updated: (CASSANDRA-1587) Explicitly expose ongoing per-node
repair tasks and est. % done
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-1587:
-----------------------------------
Issue Type: Sub-task (was: Wish)
Parent: CASSANDRA-1516
> Explicitly expose ongoing per-node repair tasks and est. % done
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1587
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: paul cannon
> Priority: Minor
>
> from my unfamiliar review of the code, it looks like this should involve exposing the number and progress of AntiEntropyService Validators. But I could be wrong.
> If a repair task involves a sub-task like compaction (see #1586), then ideally both would be visible 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.
[jira] Commented: (CASSANDRA-1587) Explicitly expose ongoing
per-node repair tasks and est. % done
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918749#action_12918749 ]
Stu Hood commented on CASSANDRA-1587:
-------------------------------------
The key complication with tracking repairs is not knowing the status of remote compactions triggered by requested trees (Validators running remotely).
> Explicitly expose ongoing per-node repair tasks and est. % done
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1587
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: paul cannon
> Priority: Minor
>
> from my unfamiliar review of the code, it looks like this should involve exposing the number and progress of AntiEntropyService Validators. But I could be wrong.
> If a repair task involves a sub-task like compaction (see #1586), then ideally both would be visible 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.