You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@helix.apache.org by "Kanak Biscuitwala (JIRA)" <ji...@apache.org> on 2014/06/26 00:30:25 UTC

[jira] [Resolved] (HELIX-440) Add scheduling layer to task framework

     [ https://issues.apache.org/jira/browse/HELIX-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kanak Biscuitwala resolved HELIX-440.
-------------------------------------

    Resolution: Fixed

Recurring schedules is now submitted. The way it was implemented was that the workflow would be cloned when it's time to run a new instance of it. If a previously started workflow is still in progress, the next one is held back (or skipped altogether if the recurrence interval is exceeded). Cleanup is implemented via the existing expiry feature. Review: https://reviews.apache.org/r/22891/

> Add scheduling layer to task framework
> --------------------------------------
>
>                 Key: HELIX-440
>                 URL: https://issues.apache.org/jira/browse/HELIX-440
>             Project: Apache Helix
>          Issue Type: Sub-task
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
>
> The task framework as-is is good for one-shot workflows, but it is useful to also specify workflows that should run at a specific time, or even repeatedly at a given cadence.
> See https://cwiki.apache.org/confluence/display/HELIX/Scheduled+Tasks for more information.



--
This message was sent by Atlassian JIRA
(v6.2#6252)