You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by 伝渏ゆ <16...@qq.com> on 2020/07/04 02:26:22 UTC
[discuss] Force Task Success
Hi everyone,
These are my ideas on the project "force task success".
(I will abbreviate it as FTS in the following text)
# Functional Requirements analysis
Since the process has two kinds of failure strategies, one is "continue" and the other is "end".
1) "end"
In this case, failure of just one task can stop and end the whole process. So, here FTS should
mark the failed node and then let other nodes continue to execute.
2) "continue"
In this case, a failed process instance may contain several failed nodes. I think we are supposed
to let the user select certain failed nodes to execute FTS.
## some details in the form of Q&A
Q: What exactly does TFS mean?
A: Briefly speaking, the system will change the states of those failed task intances, make the
process continue and log each execution of the continuing tasks.
Q: After requesting TFS, are the operating parameters (such as failure strategy, notification
strategy, priority...) inherited or can they be reset?
A: Just use the params before
Q: When sub_process fails, the target of TFS should be sub_process or the failed node in it？
A: The whole sub_process
# Implementation ideas
- For the module api-server, it needs to provide api for module UI：
1) add a new interface to deal with TFS where user could choose certain failed nodes through
parameters. This interface will insert a new type of command into the database.
2) change one interface(/projects/{projectName}/instances/list-pagings), because the cmdType
needs to add another state.
- For the module master-server:
It will change state of failed nodes, log this operation and send new task instances to worker-server.
- For the module worker-server:
It will execute new task instances and log the execution.
Really looking forward to your advice~~
Re: [discuss] Force Task Success
Posted by "lgcareer2019@outlook.com" <lg...@outlook.com>.
Hi,I think you can add the email signature.
I have a point to verify.
When should the user can change the task state?
If the final status of a task instance was failture,It's ok to change the state from failture to success.
But if the task instance is running we shouldn't change it to success.
The following I didn't understand clearly on `here FTS should
mark the failed node and then let other nodes continue to execute`.
Such as what is the means of mark the failed node and how to mark it?
> 1) "end"
In this case, failure of just one task can stop and end the whole process. So, here FTS should
mark the failed node and then let other nodes continue to execute.
DolphinScheduler(Incubator) PPMC
Gang Li 李岗
lgcareer2019@outlook.com<ma...@outlook.com>
From: 伝渏ゆ
Date: 2020-07-04 10:26
To: dev
Subject: [discuss] Force Task Success
Hi everyone,
These are my ideas on the project "force task success".
(I will abbreviate it as FTS in the following text)
# Functional Requirements analysis
Since the process has two kinds of failure strategies, one is "continue" and the other is "end".
1) "end"
In this case, failure of just one task can stop and end the whole process. So, here FTS should
mark the failed node and then let other nodes continue to execute.
2) "continue"
In this case, a failed process instance may contain several failed nodes. I think we are supposed
to let the user select certain failed nodes to execute FTS.
## some details in the form of Q&A
Q: What exactly does TFS mean?
A: Briefly speaking, the system will change the states of those failed task intances, make the
process continue and log each execution of the continuing tasks.
Q: After requesting TFS, are the operating parameters (such as failure strategy, notification
strategy, priority...) inherited or can they be reset?
A: Just use the params before
Q: When sub_process fails, the target of TFS should be sub_process or the failed node in it？
A: The whole sub_process
# Implementation ideas
- For the module api-server, it needs to provide api for module UI：
1) add a new interface to deal with TFS where user could choose certain failed nodes through
parameters. This interface will insert a new type of command into the database.
2) change one interface(/projects/{projectName}/instances/list-pagings), because the cmdType
needs to add another state.
- For the module master-server:
It will change state of failed nodes, log this operation and send new task instances to worker-server.
- For the module worker-server:
It will execute new task instances and log the execution.
Really looking forward to your advice~~
回复：[discuss] Force Task Success
Posted by Jave-Chen <ke...@foxmail.com>.
Good ideas. Could you go on with more details ?
------------------ 原始邮件 ------------------
发件人: "1606079777"<1606079777@qq.com>;
发送时间: 2020年7月4日(星期六) 上午10:26
收件人: "dev"<dev@dolphinscheduler.apache.org>;
主题: [discuss] Force Task Success
Hi everyone,
These are my ideas on the project "force task success".
(I will abbreviate it as FTS in the following text)
# Functional Requirements analysis
Since the process has two kinds of failure strategies, one is "continue" and the other is "end".
1) "end"
In this case, failure of just one task can stop and end the whole process. So, here FTS should
mark the failed node and then let other nodes continue to execute.
2) "continue"
In this case, a failed process instance may contain several failed nodes. I think we are supposed
to let the user select certain failed nodes to execute FTS.
## some details in the form of Q&amp;A&nbsp;
Q: What exactly does TFS mean?
A: Briefly speaking, the system will change the states of those failed task intances, make the
process continue and log each execution of the continuing tasks.
Q: After requesting TFS, are the operating parameters (such as failure strategy, notification
strategy, priority...) inherited or can they be reset?
A: Just use the params before
Q:&nbsp;When sub_process fails, the target of TFS should be sub_process or the failed node in it？
A: The whole sub_process
# Implementation ideas
- For the module api-server, it needs to provide api for module UI：
1) add a new interface to deal with TFS where&nbsp;user could choose certain failed nodes through
parameters. This interface will insert a new type of command into the database.
2) change one interface(/projects/{projectName}/instances/list-pagings), because the cmdType
needs to add another state.
- For the module master-server:
It will change state of failed nodes, log this operation and send new task instances to worker-server.
- For the module worker-server:
It will execute new task instances and log the execution.
Really looking forward to your advice~~