[
https://issues.apache.org/jira/browse/HELIX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157419#comment-14157419
]
ASF GitHub Bot commented on HELIX-524:
--------------------------------------
Github user dayzzz commented on the pull request:
https://github.com/apache/helix/pull/6#issuecomment-57728028
* About the interface change, IMHO, this is a nature part of the task
interface. If the existing customers want to update, adding the support is
encouraged. We can have another interface for monitoring the progress, but
doesn't seem to be a nice design.
* The task framework should call the progress interface and expose the
status somehow, discussed below.
* Persistency story, ZK is a good place if we only want to record the final
result. If we want to expose the progress as a task runs, putting these
periodical status updates in ZK is not a choice due to the large traffic,
generally ZK is not a good place for reporting and monitoring service status. I
also discussed this with Jason, we thought about inGraph (which is not an
option for open source), Kafka or Riemann. (Greg, JMX sounds a good idea.)
Without a conclusion of where to put these status stats, I agree that the
progress interface is not of much value. For the first step, it would be good
enough if we can monitor the progress. What do you guys think?
* For the bogus progress number, it's the customer themselves who need to
track the progress, if they want to see the bogus value, I'm fine with that :).
The controller should be set not to act on the bogus value by the customers.
> 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)
