You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Subhrat Chaudhary (Jira)" <ji...@apache.org> on 2023/05/16 05:03:00 UTC
[jira] [Updated] (RANGER-4240) Optimize deletion of XXAuthSession while deleting user
[ https://issues.apache.org/jira/browse/RANGER-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subhrat Chaudhary updated RANGER-4240:
--------------------------------------
Description:
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 hours, 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}
To optimize this, we can implement RANGER-3681 for deletion of records from x_auth_sess.
was:
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 is called, deletion of records from x_auth_sess can take hours. To optimize this, we can implement RANGER-3681 for deletion of records from x_auth_sess.
> 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 hours, 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}
> 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)