... so that users can avoid executing the same cron command at the same time in multiple nodes. Technically this can be done without this change by setting a different cron job schedule in each node but it requires complicated parameter setting. Change-Id: I596879d5d46f23e54fe344d5bf93a57837a6d287changes/01/846601/4
parent
daa8abd50a
commit
21c95657ef
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The ``glance::cache::cleaner`` class and the ``glance::cache::pruner``
|
||||
class now support the ``maxdelay`` parameter. This parameter would be
|
||||
useful in a multi-node deployment, to avoid launching the same cron command
|
||||
at the same time in multiple nodes.
|
Loading…
Reference in new issue