You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "fuchanghai (via GitHub)" <gi...@apache.org> on 2023/05/11 08:51:32 UTC
[GitHub] [dolphinscheduler] fuchanghai opened a new issue, #14086: [Bug] [Master] The subprocess type node is always in the ready stop state
fuchanghai opened a new issue, #14086:
URL: https://github.com/apache/dolphinscheduler/issues/14086
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
流程实例的失败策略为结束，并且选择并行策略。当subprocess类型节点很多的时候，一部分子流程实例已经运行成功，但是subprocess 在父流程中的任务实例还未更新成完成状态，此时一个subprocess 类型节点失败了，父流程会杀死所有存活的任务实例，所有存活的subprocess关联的子流程实例会被强制更新为ready stop 状态，导致父流程中的任务实例无法更新
>The failure policy of the process instance is end, and the parallelism policy is selected. When there are many subprocess type nodes, some subprocess instances have run successfully, but the subprocess task instances in the parent process have not been updated to complete status. At this time, a subprocess type node fails, and the parent process will kill all surviving tasks. instance, all surviving subprocess-associated subprocess instances will be forcibly updated to the ready stop state, resulting in task instances in the parent process not being updated
### What you expected to happen
run right
### How to reproduce
run right
### Anything else
_No response_
### Version
3.0.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14086: [Bug] [Master] The subprocess type node is always in the ready stop state
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #14086:
URL: https://github.com/apache/dolphinscheduler/issues/14086#issuecomment-1543600210
Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
* In order for us to understand your request as soon as possible, please provide detailed information, version or pictures.
* If you haven't received a reply for a long time, you can [join our slack](https://s.apache.org/dolphinscheduler-slack) and send your question to channel `#troubleshooting`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14086: [Bug] [Master] The subprocess type node is always in the ready stop state
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #14086:
URL: https://github.com/apache/dolphinscheduler/issues/14086#issuecomment-1543599607
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The failure policy of the process instance is end, and the parallelism policy is selected. When there are many subprocess type nodes, some subprocess instances have run successfully, but the subprocess task instances in the parent process have not been updated to complete status. At this time, a subprocess type node fails, and the parent process will kill all surviving tasks. instance, all surviving subprocess-associated subprocess instances will be forcibly updated to the ready stop state, resulting in task instances in the parent process not being updated
>The failure policy of the process instance is end, and the parallelism policy is selected. When there are many subprocess type nodes, some subprocess instances have run successfully, but the subprocess task instances in the parent process have not been updated to complete status. At this time, a subprocess type node fails, and the parent process will kill all surviving tasks. instance, all surviving subprocess-associated subprocess instances will be forcibly updated to the ready stop state, resulting in task instances in the parent process not being updated
### What you expected to happen
run right
### How to reproduce
run right
### Anything else
_No response_
### Version
3.0.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] zhongjiajie closed issue #14086: [Bug] [Master] The subprocess type node is always in the ready stop state
Posted by "zhongjiajie (via GitHub)" <gi...@apache.org>.
zhongjiajie closed issue #14086: [Bug] [Master] The subprocess type node is always in the ready stop state
URL: https://github.com/apache/dolphinscheduler/issues/14086
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org