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] [Commented] (AURORA-1389) Use a more strict DB transaction isolation.
Date Thu, 24 Dec 2015 20:02:49 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071211#comment-15071211
] 

Bill Farner commented on AURORA-1389:
-------------------------------------

This might be possible now that we are using {{DelayExecutor}} to block async work until a
transaction completes.

> Use a more strict DB transaction isolation.
> -------------------------------------------
>
>                 Key: AURORA-1389
>                 URL: https://issues.apache.org/jira/browse/AURORA-1389
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler, Technical Debt
>            Reporter: Bill Farner
>            Priority: Minor
>
> In AURORA-1386 it was necessary to relax the transaction isolation to match development
patterns used with MemStorage.  Now that we have a storage engine that allows for more strict
transaction isolation, it would be nice to use them.
> To support this, we need a pattern for queuing asynchronous work while performing a transaction,
but only commence the work once the transaction has successfully been committed.



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

Mime
View raw message