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/09/06 06:40:00 UTC
[GitHub] [dolphinscheduler] welsh-wen opened a new issue, #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
welsh-wen opened a new issue, #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796
### 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
### What you expected to happen
The configuration takes effect
### How to reproduce
1.Create a shell workflow
2.Configure the failure policy
3.Run the workflow and wait for it to fail
4.Observe if it retries
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] 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] DarkAssassinator commented on issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
DarkAssassinator commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1237778507
i face a somewhat similar case, i will check itand try fix it. @SbloodyS
--
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 #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1237729616
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] DarkAssassinator commented on issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
DarkAssassinator commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1238148224
@welsh-wen did u configure the timeout setting? because the timeout setting will hang the retry process.
--
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] SbloodyS commented on issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
SbloodyS commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1237779720
> i face a somewhat similar case, i will check itand try fix it. @SbloodyS
Great. I've assigned to you.
--
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] caishunfeng closed issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
caishunfeng closed issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
URL: https://github.com/apache/dolphinscheduler/issues/11796
--
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] caishunfeng commented on issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
caishunfeng commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1247494313
close by #11864
--
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] DarkAssassinator commented on issue #11796: [Bug] [WorkFlow] The failed retry configuration does not take effect
Posted by GitBox <gi...@apache.org>.
DarkAssassinator commented on issue #11796:
URL: https://github.com/apache/dolphinscheduler/issues/11796#issuecomment-1239400981
if use configre the timeout and retry, it will cause a dead loop.
because `TASK_STATE_CHANGE` state event will remove the taskProcessor
but later `TIME_OUT` state event will use this taskProcessor, it will throw a NPE:
And `WorkflowExecuteRunnable` will not remove this event if occur a Exception, so will keep a dead loop, then `WorkflowExecuteThreadPool` will keep print `The workflow has been executed by another thread`, this thread hang.
--
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