You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Sailaja Polavarapu (Jira)" <ji...@apache.org> on 2021/10/27 15:09:00 UTC
[jira] [Comment Edited] (RANGER-3319) Ranger usersync cookie
default duration for sync
[ https://issues.apache.org/jira/browse/RANGER-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434898#comment-17434898 ]
Sailaja Polavarapu edited comment on RANGER-3319 at 10/27/21, 3:08 PM:
-----------------------------------------------------------------------
[~fullhouse],
>> 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.
>>>
This issue is fixed as part of RANGER-3374
Please give it a try and re-open if the issue still exists.
was (Author: spolavarapu):
[~fullhouse],
>> 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.
>>>
This issue is fixed as part of RANGER-3374
> Ranger usersync cookie default duration for sync
> ------------------------------------------------
>
> Key: RANGER-3319
> URL: https://issues.apache.org/jira/browse/RANGER-3319
> Project: Ranger
> Issue Type: Bug
> Components: usersync
> Affects Versions: 2.1.0, 2.0.1, 2.2.0, 2.1.1
> Reporter: Konstantin Tsypin
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)