[jira] [Commented] (RANGER-4240) Optimize deletion of XXAuthSession while deleting user

["Subhrat Chaudhary (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RANGER-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723113#comment-17723113 ] 

Subhrat Chaudhary commented on RANGER-4240:
-------------------------------------------

Patch submitted for review - https://reviews.apache.org/r/74438/

> Optimize deletion of XXAuthSession while deleting user
> ------------------------------------------------------
>
>                 Key: RANGER-4240
>                 URL: https://issues.apache.org/jira/browse/RANGER-4240
>             Project: Ranger
>          Issue Type: Improvement
>          Components: admin
>            Reporter: Subhrat Chaudhary
>            Assignee: Subhrat Chaudhary
>            Priority: Major
>
> The table x_auth_session may contain records for a user in thousands. For users which are frequently used, this count is usually 10k to 15k, in some cases it can be higher.
> For such a user, when delete API 
> {code:java}
> /xusers/secure/users/id/{user_id}{code}
>  is called, deletion of records from x_auth_sess can take minutes, since rows will be locked for deletion and following exception is noticed in logs:
> {code:java}
> java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction{code}
> During testing for deletion of a user with about 30k records in x_auth_session, it took about 6.4 minutes.
> To optimize this, we can implement RANGER-3681 for deletion of records from x_auth_sess.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)