[RANGER-742] Ranger usersync fails after syncing 500 users from AD or ldap server when paged results is enabled.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0, 0.5.1
• Fix Version/s: 0.5.1, 0.6.0
• Component/s: usersync
• Assignee: Sailaja Polavarapu
• Reporter: Sailaja Polavarapu
• Created: 24/Nov/15 18:52
• Updated: 05/Dec/15 01:00
• Resolved: 01/Dec/15 22:51

Description

When Usersync is configured with AD/Ldap as the sync source, it fails to sync the users after 500 users. Following is the exception from usersync:
24 Nov 2015 12:04:31 INFO LdapUserGroupBuilder UnixUserSyncThread - Updating user count: 500, userName: user0499, groupList: group05
24 Nov 2015 12:04:31 ERROR UserGroupSync UnixUserSyncThread - Failed to initialize UserGroup source/sink. Will retry after 3600000 milliseconds. Error details:
javax.naming.CommunicationException: LDAP: error code 2 - paged results cookie is invalid; remaining name 'dc=qe,dc=hortonworks,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1849)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:339)
at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267)
at org.apache.ranger.ldapusersync.process.LdapUserGroupBuilder.updateSink(LdapUserGroupBuilder.java:310)
at org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:58)