[
https://issues.apache.org/jira/browse/SENTRY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553216#comment-15553216
]
Sravya Tirukkovalur commented on SENTRY-1486:
---------------------------------------------
Would be good to run similar tests on the other dbs that we support, that is,
oracle and postgres. But I would imagine this is a very common setting and dbs
should probably design for repeatable reads. So, how about lets file a follow
on jira to complete testing on other dbs? One way to do it would be: Dump
latency times from Sentry metrics page before and after this commit after
running our suite. That will give us atleast some relative numbers.
> 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)
