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

Posted to dev@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/01/28 23:23:35 UTC

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

Bill Farner created AURORA-138:
----------------------------------

             Summary: 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.1.5#6160)