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

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/12/28 03:47:49 UTC

[jira] [Resolved] (AURORA-138) Ensure state change side-effects occur at the end of transactions

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

Bill Farner resolved AURORA-138.
--------------------------------
    Resolution: Won't Fix

> Ensure state change side-effects occur at the end of transactions
> -----------------------------------------------------------------
>
>                 Key: AURORA-138
>                 URL: https://issues.apache.org/jira/browse/AURORA-138
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Bill Farner
>            Priority: Minor
>
> TaskStateMachine reports side-effects to perform after a task's status is altered, but these only happen near the end of the local transaction.  Because of the way transactions are executed, the local transaction may be wrapped in an outer transaction, and state is only stored after the outer-most transaction completes.  This means we could perform side-effects relevant to state that has not yet been persisted.



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