mistral/mistral/engine
Vitalii Solodilov b79f91e9ec Propagated a task timeout to a action execution
It shall be possible to specify timeout for Mistral actions in order
to cancel some long-performed action so that to provide predictable
execution time for client service.
Currently Mistral allows configure timeout on task and automatically
changes task status to error. However mistral don't interrupt action
execution.
We need Mistral to terminate timed out action execution, because there
might be the following issues:
* several the same action executions can run at the same time breaking
data consistency
* stale action executions may lead to the massive resources
consumption (memory, cpu..)

Change-Id: I2a960110663627a54b8150917fd01eec68e8933d
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
2018-01-31 17:40:52 +04:00
..
__init__.py Renaming "engine1" to "engine" 2015-04-09 17:47:36 +06:00
action_handler.py Dynamic workflow name evaluation. 2017-08-16 13:17:10 +02:00
action_queue.py Propagated a task timeout to a action execution 2018-01-31 17:40:52 +04:00
actions.py Propagated a task timeout to a action execution 2018-01-31 17:40:52 +04:00
base.py Make workflow execution creation idempotent 2018-01-04 14:07:12 +01:00
default_engine.py Propagated a task timeout to a action execution 2018-01-31 17:40:52 +04:00
dispatcher.py Add hide_args=True to @profiler.trace() where it may cause problems 2017-05-12 15:22:46 +07:00
engine_server.py Make workflow execution creation idempotent 2018-01-04 14:07:12 +01:00
policies.py Propagated a task timeout to a action execution 2018-01-31 17:40:52 +04:00
task_handler.py Gracefully handle DB disconnected connect errors 2017-12-28 16:50:19 +07:00
tasks.py Propagated a task timeout to a action execution 2018-01-31 17:40:52 +04:00
utils.py Create and run a workflow within a namespace 2017-08-01 13:51:05 +00:00
workflow_handler.py Make workflow execution creation idempotent 2018-01-04 14:07:12 +01:00
workflows.py Make workflow execution creation idempotent 2018-01-04 14:07:12 +01:00