ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Polavarapu (Jira)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-3101) Ranger usersync not recovering from initial errors in subsequent syncs
Date Thu, 17 Dec 2020 00:33:00 GMT

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

Sailaja Polavarapu updated RANGER-3101:
---------------------------------------
    Fix Version/s: 2.2.0
                   3.0.0

> 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
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: 0001-RANGER-3101-Added-code-to-handle-updating-users-in-c.patch
>
>
> 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)

Mime
View raw message