summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Harlow <harlowja@yahoo-inc.com>2015-12-10 15:36:39 -0800
committerJoshua Harlow <harlowja@yahoo-inc.com>2016-01-19 13:23:02 -0800
commit4d9925f5a702a557dccac7b19bb41004d60e8b75 (patch)
tree89a93327b7128e851914e1b11a295d7cd57cec35
parentadb31742dca9d9fd8ec4c225997d586386a7dd74 (diff)
downloadtaskflow-4d9925f5a702a557dccac7b19bb41004d60e8b75.tar.gz
Add useful/helpful comment to retry scheduler
This is hopefully useful to understand why this happens in this order. Change-Id: I8ff63417489a8d4bada12acc91dbc6bca69df2ba
-rw-r--r--taskflow/engines/action_engine/scheduler.py3
1 files changed, 3 insertions, 0 deletions
diff --git a/taskflow/engines/action_engine/scheduler.py b/taskflow/engines/action_engine/scheduler.py
index 5fdc199..1f6785b 100644
--- a/taskflow/engines/action_engine/scheduler.py
+++ b/taskflow/engines/action_engine/scheduler.py
@@ -42,6 +42,9 @@ class RetryScheduler(object):
return self._retry_action.schedule_reversion(retry)
elif intention == st.RETRY:
self._retry_action.change_state(retry, st.RETRYING)
+ # This will force the subflow to start processing right *after*
+ # this retry atom executes (since they will be blocked on their
+ # predecessor getting out of the RETRYING/RUNNING state).
self._runtime.retry_subflow(retry)
return self._retry_action.schedule_execution(retry)
else: