You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iota.apache.org by "Barbara Gomes (JIRA)" <ji...@apache.org> on 2016/12/09 03:25:58 UTC

[jira] [Assigned] (IOTA-35) Add capability to backup an orchestration and load the backup if the updated incarnation of that orchestration fails

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

Barbara Gomes reassigned IOTA-35:
---------------------------------

    Assignee: Barbara Gomes

> Add capability to backup an orchestration and load the backup if the updated incarnation of that orchestration fails 
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: IOTA-35
>                 URL: https://issues.apache.org/jira/browse/IOTA-35
>             Project: Iota
>          Issue Type: New Feature
>    Affects Versions: 0.1
>            Reporter: Omkar Prabhu
>            Assignee: Barbara Gomes
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Today when a stably running orchestration is updated, fey tries to restart the orchestration up to 3 times in a minute before giving up. 
> Instead of giving up, it would be great if fey had the capability to load the previous stable version of the orchestration.
> Not all orchestrations may need this feature. Hence, it could be a parameter in the orchestration itself which lets fey know to back it up and load backup on failure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)