aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1386) Transaction isolation on DB stores is too strict
Date Wed, 08 Jul 2015 21:02:04 GMT

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

Bill Farner updated AURORA-1386:
--------------------------------
    Sprint: Twitter Aurora Q2'15 Sprint 7

> 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)

Mime
View raw message