yahoo-eng-team team mailing list archive

[Jose Castro Leon <1935840@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

During a trust deletion, the backend will fetch all trusts belonging to
the same trustor and find if there is any delegated trust based on the
one we are deleting. So it can delete it as well.

If the backend list_trusts_for_trustor returns a considerable amount of
trusts, the whole process will load a huge amount of memory and loop
over it. On 380k trusts with no redelegation, the api call takes 35
seconds to process and 2.5 GB of memory while looping.

Just by passing the filter to the backend and filter out the trusts that
have delegation, the api call takes around a second with no further
increase in memory utilisation.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1935840

Title:
  Performance issue when deleting trusts

Status in OpenStack Identity (keystone):
  New

Bug description:
  During a trust deletion, the backend will fetch all trusts belonging
  to the same trustor and find if there is any delegated trust based on
  the one we are deleting. So it can delete it as well.

  If the backend list_trusts_for_trustor returns a considerable amount
  of trusts, the whole process will load a huge amount of memory and
  loop over it. On 380k trusts with no redelegation, the api call takes
  35 seconds to process and 2.5 GB of memory while looping.

  Just by passing the filter to the backend and filter out the trusts
  that have delegation, the api call takes around a second with no
  further increase in memory utilisation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1935840/+subscriptions