You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (Jira)" <ji...@apache.org> on 2020/12/02 16:42:00 UTC

[jira] [Updated] (RANGER-3101) Ranger usersync not recovering from initial errors in subsequent syncs

     [ https://issues.apache.org/jira/browse/RANGER-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Velmurugan Periasamy updated RANGER-3101:
-----------------------------------------
    Reporter: Abhishek Shukla  (was: Sailaja Polavarapu)

> Ranger usersync not recovering from initial errors in subsequent syncs
> ----------------------------------------------------------------------
>
>                 Key: RANGER-3101
>                 URL: https://issues.apache.org/jira/browse/RANGER-3101
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger, usersync
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Abhishek Shukla
>            Assignee: Sailaja Polavarapu
>            Priority: Major
>
> One issue noticed was that during initial sync a deadlock was detected while updating x_portal_user table which caused the initial sync failure. The subsequent syncs should have been successful, but because of a missing error case check during update of this user, subsequent syncs are also failing. 
> From the logs, I noticed that the initial DB deadlock happened for a service user. This user is being created by usersync during which I also see service creation request which also creates the service user if doesn't exist. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)