Uploaded image for project: 'Ranger'
  1. Ranger
  2. RANGER-4240

Optimize deletion of XXAuthSession while deleting user

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0, 2.4.1, 2.5.0
    • admin
    • None

    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 

      /xusers/secure/users/id/{user_id}

       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:

      java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction

      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.

      Attachments

        Issue Links

          Activity

            People

              suchnit Subhrat Chaudhary
              suchnit Subhrat Chaudhary
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: