[
https://issues.apache.org/jira/browse/HELIX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156204#comment-14156204
]
ASF GitHub Bot commented on HELIX-524:
--------------------------------------
Github user brandtg commented on the pull request:
https://github.com/apache/helix/pull/6#issuecomment-57596146
For persistence story, what about putting a new health report:
`/STAND_ALONE/INSTANCES/{instanceName}/HEALTHREPORT/taskStatus`?
Another thing to consider is that adding `#getProgress` to the task
interface requires users to be able to intelligently report task status. I
suspect that in practice someone might be annoyed at this extra responsibility,
and provide dummy numbers (sounds stupid, but saw it before).
Maybe a better approach would be to try to monitor on things we know a
priori about task (e.g. lifetime) and provide tools to inspect ones that seem
stuck (e.g. task/partition-addressable stack trace)?
> add getProgress() to Task interface
> -----------------------------------
>
> Key: HELIX-524
> URL: https://issues.apache.org/jira/browse/HELIX-524
> Project: Apache Helix
> Issue Type: Improvement
> Components: helix-core
> Affects Versions: 0.6.4
> Reporter: Hongbo Zeng
> Fix For: 0.6.5
>
>
> Add a getProgress to the Task interface, this is very helpful for long
> running tasks, from which we know the status of a task and see if it's
> blocked. The return value is a double, ranging from 0 to 1.0, 1.0 indicates a
> task is finished
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
