The documentation you're currently reading is for version 3.0.0. Click here to view documentation for the latest stable version.
This section contains information on how to troubleshoot Mistral-related issues.
Troubleshooting Mistral Database Upgrade¶
mistral-api services must not be running at time of upgrading the st2mistral
package and the Mistral database schema. If the st2mistral package has been upgraded and the
services are started before the
mistral-db-manage upgrade head CLI command is executed, then the
mistral-db-manage upgrade head command may fail.
mistral-api services run, SQLAlchemy automatically creates tables,
relationships, and indices that do not exist. If there are new database objects in the upgraded
database schema, the
mistral-db-manage upgrade head command will fail because the actual schema
in the database is now different than its specifications, and it no longer can create the new database
When that happens, the new database tables, relationships, and indices must be deleted before the
mistral-db-manage upgrade head command can be re-run. For more details, review the version-specific
notes in the Upgrades documentation, for the version of Mistral and EWC you are upgrading
Troubleshooting Mistral Workflow Completion Latency¶
Since v2.7, the results tracking mechanism is replaced with a callback mechanism from Mistral. Instead of EWC querying Mistral at regular intervals, Mistral is configured to callback EWC on task and workflow completion. See Mistral Workflows Completion, Latency, and Performance
Prior to v2.7, EWC queries Mistral to check on workflow execution status and the status of individual tasks
via st2resultstracker. This
st2resultstracker process saves the state of outstanding workflow executions
in the database, and once a workflow is complete, deletes the state from the database. The process uses
eventlets to simultaneously query multiple workflow results. This can consume significant CPU cycles.
There are two configurable values for controlling this. These are
thread_pool_size (number of eventlets)
query_interval (interval to space out the subsequent queries to Mistral for a single execution). You
can configure these values by editing the
results_tracker section in
[resultstracker] query_interval = 5 # in seconds thread_pool_size = 10
These values are subject to load conditions in your infrastructure and the number of workflows
you are running. The default value for
query_interval is set to
5 (seconds) which is a balance
between the workflow speed and the CPU overhead. With EWC 2.2 and earlier, this value was
We have now set the default value to
5 seconds to be conservative. This also means the time to detect
a completed workflow in Mistral by EWC could take as long as 5 seconds.
If this is unacceptable for you, you can reduce the
query_interval and also
simultaneously check CPU usage for the