Cron triggers can't be disabled even if they are not used
Bug #1724147 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Renat Akhmerov |
Bug Description
In many installations cron triggers are not used at all but the subsystem starts anyway and consumes resources. We need to have a config option to disable it.
Changed in mistral: | |
milestone: | none → queens-1 |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in mistral: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/512520 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=6efe094012d e5458ac66bbaf93 a38005b8e69c2d
Committed: https:/
Submitter: Zuul
Branch: master
commit 6efe094012de545 8ac66bbaf93a380 05b8e69c2d
Author: Renat Akhmerov <email address hidden>
Date: Tue Oct 17 14:09:36 2017 +0700
Add a config option to disable cron triggers
* Cron triggers (implemented in periodic.py) are always enabled cron_trigger_ thread" pecan app config variable
although in many installations they are not needed. When they
are enabled they consume resoruces (keep polling DB etc.).
This patch add the config option "enabled" under "cron_trigger"
group that can be used to disable the entire subsystem.
* Wiped out "disable_
that was use to disable cron triggers in unit tests in favor of
the new config option
* Other minor style changes
Closes-bug: #1724147 3ea8696b7cd6547 2c8a49937bf
Change-Id: I79b9ccb2f4286b