You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/06/28 21:00:00 UTC

[jira] [Updated] (SENTRY-1824) SentryStore may serialize transactions that rely on unique key

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

Na Li updated SENTRY-1824:
--------------------------
    Attachment: SENTRY-1824.001-sentry-ha-redesign.patch

v1. add "synchronized" for each SentryStore function that update permissions.

> SentryStore may serialize transactions that rely on unique key
> --------------------------------------------------------------
>
>                 Key: SENTRY-1824
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1824
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Na Li
>              Labels: sentry-ha
>             Fix For: sentry-ha-redesign
>
>         Attachments: SENTRY-1824.001-sentry-ha-redesign.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> The suggestion came from [~lina.li] during the review for SENTRY-1821.
> We have several places where we rely on transactions to support read/modify/write semantics for incrementing IDs. This works but using DB support is rather expensive and we can user in-core serializations to help with this at least within a single node and rely on DB for multi-node synchronization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)