[
https://issues.apache.org/jira/browse/SENTRY-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347467#comment-14347467
]
Arun Suresh commented on SENTRY-664:
------------------------------------
Committed :
{noformat}
Repository: incubator-sentry
Updated Branches:
refs/heads/master dd9edc666 -> feb8cbee6
SENTRY-664: Fix to ensure path updates are synced after namenode restart
(Reviewed by Prasad)
Project: http://git-wip-us.apache.org/repos/asf/incubator-sentry/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-sentry/commit/feb8cbee
Tree: http://git-wip-us.apache.org/repos/asf/incubator-sentry/tree/feb8cbee
Diff: http://git-wip-us.apache.org/repos/asf/incubator-sentry/diff/feb8cbee
Branch: refs/heads/master
Commit: feb8cbee60e2d8d36667737d527c602de3e15d13
Parents: dd9edc6
Author: Arun Suresh <Arun Suresh>
Authored: Wed Mar 4 11:52:53 2015 -0800
Committer: Arun Suresh <Arun Suresh>
Committed: Wed Mar 4 11:52:53 2015 -0800
{noformat}
> After Namenode is restarted, Path updates remain unsynched
> ----------------------------------------------------------
>
> Key: SENTRY-664
> URL: https://issues.apache.org/jira/browse/SENTRY-664
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Labels: sentry-hdfs
> Attachments: SENTRY-664.1.patch
>
>
> Path updates remain un-synced after a Namenode restart.
> Ideally, after a restart, the Namenode receives both the Path and Permission
> updates from sentry service. These updates are ordered by a sequence Id. Also
> the first Path/Permission update is supposed to be a FULL update.
> From observing the logs, It looks like after namenode restart, the sequence
> of PathsUpdate objects do not start with a FULL update (The
> PermissionsUpdates are fine though). Thus the namenode remains unsynched with
> respect to path information.
> A workaround is to restart the metastore after the namenode has restarted.
> This will ensure HMS will send a FULL update to Sentry. This will cause
> Sentry service will flush its existing update queue, so the next time the
> namenode asks for an update, this FULL update will be sent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
