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/07/08 23:02:04 UTC

[jira] [Created] (AURORA-1386) Transaction isolation on DB stores is too strict

Bill Farner created AURORA-1386:
-----------------------------------

             Summary: Transaction isolation on DB stores is too strict
                 Key: AURORA-1386
                 URL: https://issues.apache.org/jira/browse/AURORA-1386
             Project: Aurora
          Issue Type: Bug
          Components: Scheduler
            Reporter: Bill Farner
            Assignee: Bill Farner
            Priority: Critical


The transaction isolation used in the scheduler's DB-based storage is too strict.  This results in inconsistent data when work in a transaction forks asynchronous work on a different thread, which is implicitly done for messages on the event bus.  In cases like {{TaskThrottler}} which has some preconditions around expected state, we encounter exceptions related to the ancestor state not yet being shown as terminated as we try to calculate the reschedule delay.



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