sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kalyan kumar kalvagadda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.
Date Thu, 11 Jan 2018 17:37:00 GMT

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

kalyan kumar kalvagadda commented on SENTRY-2115:
-------------------------------------------------

There are couple of ways to solve this
1. By clearing MAuthzPathsMapping and MAuthzPathsSnapshotId information when HDFS-SYNC is
disabled.
2. Continue to update MAuthzPathsMapping and MAuthzPathsSnapshotId even when  HDFS-SYNC is
disabled. That way when the feature is enabled sentry-namenode plug-in gets the latest snapshot.
Downside for this approach is that, sentry would be spending CPU cycles and memory processing
and storing the patch changes in MSentryPathChange and MAuthzPathsMapping.

> Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.
> -----------------------------------------------------------------------------------
>
>                 Key: SENTRY-2115
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2115
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: kalyan kumar kalvagadda
>            Assignee: kalyan kumar kalvagadda
>
> On disabling HDFS sync, HMSFollower would update the SENTRY_HMS_NOTIFICATION_ID table
but not the MSentryPathChange table.
> When  HDFS sync is enabled again, HMSFollower would continue fetching new notifications
and process them and update the MSentryPathChange and MAuthzPathsMapping info. This is not
correct. 



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

Mime
View raw message