GitHub user dasahcc opened a pull request:
https://github.com/apache/helix/pull/154
Support Workflow/Job level timeout
This PR contains:
1. Workflow level timeout feature support
2. Job level timeout fix
3. Maintenance allows 0 instances down setting.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dasahcc/helix master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/helix/pull/154.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #154
----
commit d742d09846c8b39cd46c9d8560ca856355530a88
Author: Junkai Xue <jxue@...>
Date: 2018-02-08T23:22:18Z
Fix Job level timeout not timeout jobs and refactor logics
There is an issue that job does not get timeouted. The rebalancerSchduler
is not got scheduled when job started. Fixed this issue.
Refactor the logics to support workflow level timeout.
commit debb9bb23125f4c073a3dba75bc16df3558e0c35
Author: Junkai Xue <jxue@...>
Date: 2018-02-09T01:15:41Z
Support Workflow level timeout
Current Helix supports job level timeout, we believe it does make sense to
support workflow level timeout, when users are confident with workflow running
time. It could be used for following cases:
1. Prevent long run workflows stuck there forever.
2. If someone pause the workflow forget to resume back, workflow can be
terminated with timeout.
commit e1176fe406e3a585b7d5860bf55862fc13df1b82
Author: Junkai Xue <jxue@...>
Date: 2018-02-15T01:30:37Z
Let allowed down instance number can be 0
Current the number of down instance could be 0. It will be ignored if it
set to be 0. But 0 is a valid case for not allowing any instances down.
----
---
