This bug is not valid. The task needs to run periodically to expire any
reservations that should be expired ahead of QUOTAS.reserve() calls.
The only alternative is to expire reservations explicitly before every
single QUOTAS.reserve()... which is not as performant.
This task doesn't necessarily belong in nova-scheduler. It really could
easily be moved to nova-conductor or nova-compute or something... but it
needs to run somewhere!
** Changed in: nova
Status: Confirmed => Invalid
--
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/1212028
Title:
SchedulerManager._expire_reservations doesn't need to always be
running
Status in OpenStack Compute (Nova):
Invalid
Bug description:
The nova-scheduler log is filled with:
2013-08-13 23:30:56.219 730 DEBUG nova.openstack.common.loopingcall [-]
Dynamic looping call sleeping for 60.00 seconds _inner
/opt/stack/nova/nova/openstack/common/loopingcall.py:132
2013-08-13 23:31:56.228 730 DEBUG nova.openstack.common.periodic_task [-]
Running periodic task SchedulerManager._expire_reservations run_periodic_tasks
/opt/stack/nova/nova/openstack/common/periodic_task.py:176
This periodic task is to help the quota system work, but if the
scheduler hasn't done anything for the past few minutes there is no
reason to keep running this task. Instead it can be restarted upon
the next scheduling event.
The main benefit from fixing this will be cleaner nova-scheduler log
files
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1212028/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
