sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sravya Tirukkovalur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-1101) When edit log for HDFS sync in Sentry Server is full, the next Path update is not correctly setup
Date Tue, 29 Mar 2016 03:50:25 GMT

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

Sravya Tirukkovalur commented on SENTRY-1101:
---------------------------------------------

Thanks for the test case [~hahao]! I looked at the code more closely. The updatelog size is
100 (it is not configurable). When 101 path update is received by Sentry, it as usual adds
it to the updateable (UpdateableAuthzPaths)- compacted version of path changes, and then tries
to append it to the updatelog. As updatelog size is now 100, it compacts the existing updateable
into the head of update log. So I do not see what exactly is not being handled correctly.
Could you elaborate?

> When edit log for HDFS sync in Sentry Server is full, the next Path update is not correctly
setup
> -------------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-1101
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1101
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>            Reporter: Hao Hao
>            Assignee: Hao Hao
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-1101.0.patch
>
>
> The edit log for caching the path updates is not updated properly once the cache is full
in Sentry Server side. In that case, even though the path updates will be send to NN plugin,
the path updates itself is not containing the correct paths. It can cause unexpected ACL behavior
issues during table creation. 



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

Mime
View raw message