[jira] [Comment Edited] (SENTRY-1486) Sentry should use repeatable-read consistency level

["Sravya Tirukkovalur (JIRA)" <ji...@apache.org>]

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

Sravya Tirukkovalur edited comment on SENTRY-1486 at 10/5/16 8:46 PM:
----------------------------------------------------------------------

[~akolb] Thanks for running a mini bench mark. Thats useful. By the way, which databases did you try it on? 


was (Author: sravya):
[~akolb] Which databases did you try it on?

> Sentry should use repeatable-read consistency level
> ---------------------------------------------------
>
>                 Key: SENTRY-1486
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1486
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 1.7.0, sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Alexander Kolbasov
>         Attachments: SENTRY-1486.001.patch, SENTRY-1486.002.patch
>
>
> Currently Sentry uses the "read-committed" consistency level which is the default for the Datanucleus JDO library. This causes potential problems since the state visible to each transaction can actually see updates from another transactions, so it is very difficult to reason about any code that reads multiple pieces of data.
> Instead it should use repeatable read" consistency which guarantees that any transaction only sees the state at the beginning of a transaction plus any updates done within a transaction.



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