Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Master] The subprocess type node is always in the ready stop state(3.1.x) #14169

Closed
3 tasks done
Tracked by #14168
fuchanghai opened this issue May 22, 2023 · 2 comments
Closed
3 tasks done
Tracked by #14168
Labels
bug Something isn't working Waiting for reply Waiting for reply

Comments

@fuchanghai
Copy link
Member

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

父流程实例的失败策略为结束,并且选择并行策略。当subprocess类型节点很多的时候,一部分子流程实例已经运行成功,但是subprocess 在父流程中的任务实例还未更新成完成状态,此时一个subprocess 类型节点失败了,父流程会杀死所有存活的任务实例,所有存活的subprocess关联的子流程实例会被强制更新为ready stop 状态,导致父流程中的任务实例无法更新,所以一直显示提交成功,或者运行中状态

The failure policy of the parent 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

be right

How to reproduce

be right

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@fuchanghai fuchanghai added bug Something isn't working Waiting for reply Waiting for reply labels May 22, 2023
@github-actions
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

The failure strategy of the parent process instance is end, and the parallelism strategy 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 able to be updated, so it always shows that the submission is successful, or the running state

The failure policy of the parent 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

be right

How to reproduce

be right

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@github-actions
Copy link

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 and send your question to channel #troubleshooting

fuchanghai pushed a commit to fuchanghai/dolphinscheduler that referenced this issue May 22, 2023
zhuangchong pushed a commit that referenced this issue May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for reply Waiting for reply
Projects
None yet
Development

No branches or pull requests

2 participants