[RANGER-3319] Ranger usersync cookie default duration for sync

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0, 2.0.1, 2.2.0, 2.1.1
• Fix Version/s: 2.2.0
• Component/s: usersync
• Assignee: Sailaja Polavarapu
• Reporter: Konstantin Tsypin
• Created: 15/Jun/21 15:50
• Updated: 27/Oct/21 15:08
• Resolved: 27/Oct/21 15:08

Description

Hi!

At this moment we cant initial sync out of the box our LDAP with 10k+ users & groups.

It's because sync works as three steps:

1) Sync groups

2) Sync users

3) Map users&groups as one request and send it to rangeradmin

From time to time our third step on initial sync generate this single request for a long time

It can be easily three or four hours.

Acrossing this timegate we have an error with timeout usersync cookie (that by default is 60 minutes) and failed 3rd step.

 

The workaround - is 

ranger_admin_directory/ews/webapp/WEB-INF/web.xml
change 
default 
<session-timeout>60</session-timeout> 
to just in case
<session-timeout>1440</session-timeout>

BUT im was really frustrated with this behavior whan faced it first time, and i want to have a mechanism to split mapping step for a smaller part, and update cookie from time to time. 

 

Thank you.

Issue Links

• is fixed by: RANGER-3374 Syncing 300K+ user group mappings to ranger is causing ranger to go out of memory