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

Hadoop QA commented on SENTRY-1824:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12875088/SENTRY-1824.003-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2940/console

This message is automatically generated.

> 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, 
> SENTRY-1824.002-sentry-ha-redesign.patch, 
> SENTRY-1824.003-sentry-ha-redesign.patch, 
> SENTRY-1824.004-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 isn't much of a problem for path updates since they are driven by 
> HMSFollower which usually runs on a single leader node, but permission 
> updates originate from clients directly and may be highly concurrent.
> We are internally serializing all permissions update anyway, so doing partial 
> serialization on every node helps.
> The patch serializes all calls that affect permission updates.



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

Reply via email to