Yes, thats the idea. With helix-ipc this will be possible rt? This can be extended to write rebalancers that talk to nodes to get the high water mark to decide new master. what do you think?
On Thu, Oct 9, 2014 at 3:28 PM, ASF GitHub Bot (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/HELIX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165886#comment-14165886 > ] > > ASF GitHub Bot commented on HELIX-524: > -------------------------------------- > > Github user zzhang5 commented on the pull request: > > https://github.com/apache/helix/pull/6#issuecomment-58587902 > > If we are not using ZK to invoke these methods, are we opening some > kind of end-point e.g. via Netty or JMX on each participant? > > > > > > 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) >
