You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/09/14 14:47:00 UTC

[jira] [Created] (ARIA-379) Inconsistent behavior for cancelled/failed execution tasks

Ran Ziv created ARIA-379:
----------------------------

             Summary: Inconsistent behavior for cancelled/failed execution tasks
                 Key: ARIA-379
                 URL: https://issues.apache.org/jira/browse/ARIA-379
             Project: AriaTosca
          Issue Type: Bug
            Reporter: Ran Ziv
            Priority: Minor


The {{ProcessExecutor}} will terminate subprocesses when an execution is cancelled/failed, which will stop the operations still running right away.

However, in the {{ThreadExecutor}}, such already-running operations will run until completion, regardless of the execution's state.

Need to figure out if there's a way to overcome this inconsistency across different executors, and provide a single semantic for cancelled/failed workflow executions




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)