yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

** No longer affects: nova/folsom

-- 
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/1133495

Title:
  AggregateInstanceExtraSpecs very slow

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  This bug report is here to be able to link the patch (to be commited)
  to the bug reported in the mailinglist by Sam Morrison

  I quote:

  ---------

  I have been playing with the AggregateInstanceExtraSpecs filter and
  can't get it to work.

  In our staging environment it works fine with 4 compute nodes, I have
  2 aggregates to split them into 2.

  When I try to do the same in our production environment which has 80
  compute nodes (splitting them again into 2 aggregates) it doesn't
  work.

  nova-scheduler starts to go very slow,  I scheduled an instance and
  gave up after 5 minutes, it seemed to be taking ages and the host was
  at 100% cpu. Also got about 500 messages in rabbit that were
  unacknowledged.

  We are running stable/folsom. Does anyone else have this issue or know
  if there have been any fixes in Grizzly relating to this? I couldn't
  see any bugs about it.

  Thanks,
  Sam

  ---------

  A brief discussion followed, indicating this appears to be a bug
  indeed, not a missing index. We're experiencing and seeing the same
  behavior, and I think I've found the root cause.

  From what I can see, there's a many-To-many relation defined in
  nova/db/sqlalchemy/models.py between Aggregate class and both
  AggregateHost and AggregateMetadata classes. This should be a one to
  many relation if I'm not mistaken, so I've created a patch to reflect
  this.

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