On Sun, Feb 24, 2013 at 3:31 PM, Sam Morrison <sorrison at gmail.com> wrote: > 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. > > what does the nova-scheduler log say? Where is the unacknowledged rabbitmq messages sent from? > 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 > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130225/9330a191/attachment.html>