Public bug reported: 1. Some upgrade procedures work on each projects/users rows, one by one. This is really slower than working on batches of rows.
2. Some upgrade procedures work on all rows in a single requests. This does not work with Galera because of max transaction size (https://www.percona.com/blog/2015/10/26/how-big-can-your-galera-transactions-be/) See https://etherpad.openstack.org/p/YVR-rocky-keystone-feedback ** Affects: keystone Importance: Undecided Assignee: Romain LE DISEZ (rledisez) Status: In Progress -- 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/1772988 Title: Upgrade procedure performance issues Status in OpenStack Identity (keystone): In Progress Bug description: 1. Some upgrade procedures work on each projects/users rows, one by one. This is really slower than working on batches of rows. 2. Some upgrade procedures work on all rows in a single requests. This does not work with Galera because of max transaction size (https://www.percona.com/blog/2015/10/26/how-big-can-your-galera-transactions-be/) See https://etherpad.openstack.org/p/YVR-rocky-keystone-feedback To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1772988/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
