[jira] Updated: (ODE-587) Defer deletion of instances and associtated data when process is re-deployed

["Sean Ahn (JIRA)" <ji...@apache.org>]

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

Sean Ahn updated ODE-587:
-------------------------

    Affects Version/s: 1.2
        Fix Version/s: 1.2
              Summary: Defer deletion of instances and associtated data when process is re-deployed  (was: defer deletion of instances and associtated date when process is re-deployed)

> Defer deletion of instances and associtated data when process is re-deployed
> ----------------------------------------------------------------------------
>
>                 Key: ODE-587
>                 URL: https://issues.apache.org/jira/browse/ODE-587
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>            Reporter: Sean Ahn
>            Priority: Minor
>             Fix For: 1.2
>
>
> During re-deployment of a process, any instances for the prior process are deleted together. When you have really many instances, this can take up quite some time and forces non-deterministic length of database transaction.
> 1. split the single big transaction into multiple small transactions
> 2. Ideally, process should be re-deployed right away and instances for old process should be ignored by the new process. Then, the instances for the old process get deleted with a lower priority.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.