[
https://issues.apache.org/jira/browse/RANGER-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781562#comment-15781562
]
Sailaja Polavarapu commented on RANGER-1211:
--------------------------------------------
[~bganesan]
As far as I know incremental sync is initiated only for Ranger and no other
components are currently having this behavior. The approach I specified is very
similar to the one documented in Microsoft AD for polling the changes.
https://msdn.microsoft.com/en-us/library/ms677627(v=vs.85).aspx
[~bosco]
Both "uSNChanged" and "modifyTimeStamp" are system properties on the server
and are always available. And on the Ranger side these are hardcoded attributes
and are not configurable. In any case if the admin user performing the sync has
no privileges to these attributes, then the server will not return these
properties and we will fall back to full sync.
> Improve Ranger Usersync to sync AD/LDAP users and/or groups incrementally.
> ---------------------------------------------------------------------------
>
> Key: RANGER-1211
> URL: https://issues.apache.org/jira/browse/RANGER-1211
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
> Affects Versions: 0.6.1, 0.6.2
> Reporter: Sailaja Polavarapu
> Assignee: Sailaja Polavarapu
> Labels: ranger
> Fix For: 0.7.0
>
> Attachments: DeltaSyncsupportforRangerUsersync.docx
>
>
> During every sync cycle, Ranger Usersync performs full LDAP/AD sync and
> computes the delta in-memory and updates ranger admin. Since usersync
> computes the delta (including group memberships) of all the users that are
> sync’d in memory for every sync cycle, UserSync can take a lot of resources
> on the server it is running on.
> Enhance usersync to perform full sync only during startup and incremental or
> delta sync for the subsequent sync cycles. This way the delta computation of
> group memberships can be highly reduced and can increase usersync
> performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
