Upgrade procedure performance issues

Bug #1772988 reported by Romain LE DISEZ
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone (master)

Fix proposed to branch: master
Review: https://review.openstack.org/570247

Changed in keystone:
assignee: nobody → Romain LE DISEZ (rledisez)
status: New → In Progress
Changed in keystone:
importance: Undecided → Medium
tags: added: sql
tags: added: performance
Changed in keystone:
milestone: none → rocky-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on keystone (master)

Change abandoned by Romain LE DISEZ (<email address hidden>) on branch: master
Review: https://review.opendev.org/570247
Reason: Outdated. It was for Keystone 11.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.