WBE request transition_timeout timeout not long enough
Bug #1356002 reported by
Joshua Harlow
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
taskflow |
Fix Released
|
Medium
|
Joshua Harlow |
Bug Description
When a worker is overloaded (or heavily loaded) or workers are still coming online the default timeout of 60 seconds may not be enough time for the sent task to transition out of the WAITING (submitted to worker but worker has not started it yet) or PENDING (no avaiable worker currently exits) state, when the timeout is always set to 60 seconds it can be painful to use the WBE in situations where it is more appropriate to set the timeout to higher or lower values (or infinite by setting the timeout to None).
summary: |
- WBE request timeout not long enough + WBE request transition_timeout timeout not long enough |
Changed in taskflow: | |
assignee: | nobody → Joshua Harlow (harlowja) |
importance: | Undecided → Medium |
Changed in taskflow: | |
milestone: | none → next-juno |
Changed in taskflow: | |
milestone: | next-juno → next-kilo |
Changed in taskflow: | |
status: | Fix Committed → Fix Released |
Changed in taskflow: | |
status: | Fix Released → Fix Committed |
Changed in taskflow: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/113623
Review: https:/