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

Posted to commits@sentry.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2015/03/04 01:50:05 UTC

[jira] [Created] (SENTRY-664) After Namenode is restarted, Path updates remain unsynched

Arun Suresh created SENTRY-664:
----------------------------------

             Summary: 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


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)