Integrity checker is too greedy
Bug #1801876 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Renat Akhmerov |
Bug Description
Workflow execution integrity checker may be too aggressive in case of a very big long running workflow. When a big workflow is running it may have many task executions in RUNNING state at the same time and the checker tries to process them all at once in a single transaction, so, in fact, it may block normal action completion processing for a significant period of time, even causing DB deadlocks (by timeout).
It makes sense to use batches when running this mechanism.
Changed in mistral: | |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
milestone: | none → stein-1 |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in mistral: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/615720 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=3b4136ff1eb 27472cb6d2ee4d1 603e2b92f22ac9
Committed: https:/
Submitter: Zuul
Branch: master
commit 3b4136ff1eb2747 2cb6d2ee4d1603e 2b92f22ac9
Author: Renat Akhmerov <email address hidden>
Date: Tue Nov 6 11:17:38 2018 +0700
Add batch size for integrity checker
* Added the new property 'execution_ integrity_ check_batch_ size'
under the [engine] group to limit the number of task executions
that the integrity checker may process during one iteration.
Closes-Bug: #1801876 bff109617cb15d5 6c54575dd4f
Change-Id: I3c5074c45c476e