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

Posted to dev@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/02/01 11:51:51 UTC

[jira] [Updated] (ARIA-79) Handle attributes update concurrency issues

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

Ran Ziv updated ARIA-79:
------------------------
    Summary: Handle attributes update concurrency issues  (was: Handle concurrency issues when running multiple operations)

> Handle attributes update concurrency issues
> -------------------------------------------
>
>                 Key: ARIA-79
>                 URL: https://issues.apache.org/jira/browse/ARIA-79
>             Project: AriaTosca
>          Issue Type: Bug
>            Reporter: Ran Ziv
>            Assignee: Dan Kilman
>
> It seems like currently, the scope of the storage session is too large, meaning that when one operation commits changes to the storage (e.g. updating a task's state) then runtime properties that are being modified by another will get committed too.
> Need to look into how to isolate / lock / separate these sessions (possibly via subtransactions?)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)