alei1206 opened a new issue, #15038: URL: https://github.com/apache/dolphinscheduler/issues/15038
### 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 - two dag：a -> b -> c，dependent _1 -> d -> e - Retry after failure is configured for task b. - dependent _1 is Dependent task and depends on task b. - When task b fails but the maximum number of retries is not reached, dependent _1 task fails. 中文： - 两个工作流：a -> b -> c，dependent _1 -> d -> e - 其中任务b配置了失败重试，比如最大重试次数为3，重试间隔为3min - 任务dependent _1是一个Dependent类型的任务，依赖任务b，依赖定义如下图 - 结果：当任务b失败一次后，就会触发dependent _1任务失败。  ### What you expected to happen In my opinion, after failed retry is configured for task b, dependent tasks need to wait for the retry to complete before their execution results can be calculated 中文： 我认为，如果任务b配置了失败重试，依赖任务b的Dependent任务需要等待其**执行成功或者执行失败且达到最大重试次数**后才能计算Dependent任务的依赖结果，而不是在任务b失败一次后就触发dependent _1任务失败，因为任务b处于失败重试阶段，此任务并未结束。 ### How to reproduce I think that when calculating the dependency result of a dependent task, it is necessary to additionally determine whether the dependent task has a failed retry stage to prevent the dependent task from failing due to a single failure of the dependent task. 中文： 我认为，在计算Dependent类型任务的依赖结果时，需要额外判断被依赖任务是否处于失败重试阶段，防止因为被依赖任务单次失败造成Dependent类型任务失败。 ### Anything else _No response_ ### Version 3.1.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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
