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/12/24 09:51:49 UTC

[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #13272: [Bug] [Master] resume failure processInstance state remain failure

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

   ### 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
   
   Workflow process instance resume from failure state, and all task run success actully, but task instance and process intance remain failure. And when you click resume again, all switch to success.
   
   Checking task log, the task has submit and run success when resume.
   
   Checking database table `t_ds_task_instance`. There two record, old one state is failure, and new one is success. Which make sense.
   ![企业微信截图_20221224173844](https://user-images.githubusercontent.com/16650282/209430139-7495d810-8556-4512-beab-06d8f8ae01ac.png)
   
   Since task is success, why ds judge it faliure and show failure on ui. Digging the ui http query, we found that it query both two record and return it, because of the `flag`.
   ![企业微信截图_20221224174251](https://user-images.githubusercontent.com/16650282/209430314-3a1d54d8-7c03-4c70-be63-74032a4dacbc.png)
   ![企业微信截图_20221224174335](https://user-images.githubusercontent.com/16650282/209430346-d6336206-ea39-456b-9c99-3ee61692d489.png)
   ![企业微信截图_20221224174406](https://user-images.githubusercontent.com/16650282/209430350-028703aa-f4ed-49a0-97a4-53f1a4a5ad28.png)
   ![企业微信截图_20221224174501](https://user-images.githubusercontent.com/16650282/209430373-7ea10350-d4e6-4715-a3db-964a56e80bd5.png)
   
   
   
   And I don't know what happen, thx for help.
   
   ### What you expected to happen
   
   both task instance and process instance should change to success
   
   ### How to reproduce
   
   1. create a workflow with task which suppose to run fail, and configure retry 3 times
   2. run workflow. task instance state should be failure and waiting to retry, and process instance stay running
   3. click stop. task instance state should be failure and process instance state should be stoped
   4. modify task make it will run success
   5. click resume
   6. task has submit and run. but when it finish, both task and process instance state change to failure
   7. click resume again
   8. both task and process change to success
   
   ### Anything else
   
   we are on v2.0.7
   
   ### Version
   
   2.0.x
   
   ### 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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org