You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/05/06 08:55:15 UTC

[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #9916: [Bug] [Master] Dependent Node Did Not Retry

github-actions[bot] commented on issue #9916:
URL: https://github.com/apache/dolphinscheduler/issues/9916#issuecomment-1119400038

   ### 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 dependent node did not retry after fail sometimes running after retry.
   And the lastest task instance execute duration is null
   ![图片](https://user-images.githubusercontent.com/25319167/167099254-139aa110-f39e-4eb5-b80f-76a2bedce842.png)
   
   
   ### What you expected to happen
   
   All dependent node should retry with the config
   
   ### How to reproduce
   
   1. Create about 10 process definition  instance with dependent node(another process definition), set the retry times(20) and retry interval(5 mins).
   2. Ensure the dependent process definition state is fail.
   3. Run all the process definition which has dependent node.
   4. Found some  process instance with not trigger retry after taskinstance fail
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   2.0.5
   
   ### 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