yahoo-eng-team team mailing list archive

[Mohammed Naser <1822613@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The online_data_migrations should be ran after an upgrade and contains a
list of tasks to do to backfill information after an upgrade, however,
some of those queries are extremely inefficient which results in this
online data migrations taking an unacceptable period of time.  The SQL
query that takes a really long time in question:

> SELECT count(*) AS count_1
> FROM (SELECT instance_extra.created_at AS instance_extra_created_at,
> instance_extra.updated_at AS instance_extra_updated_at,
> instance_extra.deleted_at AS instance_extra_deleted_at,
> instance_extra.deleted AS instance_extra_deleted, instance_extra.id AS
> instance_extra_id, instance_extra.instance_uuid AS
> instance_extra_instance_uuid
> FROM instance_extra
> WHERE instance_extra.keypairs IS NULL AND instance_extra.deleted = 0) AS anon_1

It would also be good for us to *not* run a data migration again if we
know we've already gotten found=0 when online_data_migrations is running
in "forever-until-complete".  Also, the value of 50 rows per run in that
mode is quite small.

ref: http://lists.openstack.org/pipermail/openstack-
discuss/2019-April/004397.html

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Inefficient queries inside online_data_migrations

Status in OpenStack Compute (nova):
  New

Bug description:
  The online_data_migrations should be ran after an upgrade and contains
  a list of tasks to do to backfill information after an upgrade,
  however, some of those queries are extremely inefficient which results
  in this online data migrations taking an unacceptable period of time.
  The SQL query that takes a really long time in question:

  > SELECT count(*) AS count_1
  > FROM (SELECT instance_extra.created_at AS instance_extra_created_at,
  > instance_extra.updated_at AS instance_extra_updated_at,
  > instance_extra.deleted_at AS instance_extra_deleted_at,
  > instance_extra.deleted AS instance_extra_deleted, instance_extra.id AS
  > instance_extra_id, instance_extra.instance_uuid AS
  > instance_extra_instance_uuid
  > FROM instance_extra
  > WHERE instance_extra.keypairs IS NULL AND instance_extra.deleted = 0) AS anon_1

  It would also be good for us to *not* run a data migration again if we
  know we've already gotten found=0 when online_data_migrations is
  running in "forever-until-complete".  Also, the value of 50 rows per
  run in that mode is quite small.

  ref: http://lists.openstack.org/pipermail/openstack-
  discuss/2019-April/004397.html

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