aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-138) Ensure state change side-effects occur at the end of transactions
Date Tue, 28 Jan 2014 22:23:35 GMT
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)

Mime
View raw message