[2.0.3][dolphinscheduler-server] process instance is always running

[zwZjut]

Purpose of the pull request

#7700
#7698

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (2.0.3-prepare@6aaecdb). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head cac0693 differs from pull request most recent head ea9639e. Consider uploading reports for the commit ea9639e to get more accurate results

@@               Coverage Diff                @@
##             2.0.3-prepare    #7914   +/-   ##
================================================
  Coverage                 ?   31.15%           
  Complexity               ?     1556           
================================================
  Files                    ?      435           
  Lines                    ?    14956           
  Branches                 ?     1500           
================================================
  Hits                     ?     4659           
  Misses                   ?     9836           
  Partials                 ?      461           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6aaecdb...ea9639e. Read the comment docs.

[caishunfeng]

LGTM

[sonarqubecloud]

SonarCloud Quality Gate failed.   

24 Bugs
0 Vulnerabilities
3 Security Hotspots
355 Code Smells

16.1% Coverage
1.0% Duplication

[lenboo]

@zwZjut @caishunfeng Well done! At the same time , i think we can add some descriptions what these changes would affect.
Eg :

1. The killing process of workflow.
2. ...

[lenboo]

+1

[caishunfeng]

Mainly stability optimization:

• Fixed that in some cases concurrent consumption of events resulted in no consumption, resulting in the workflow instance running all the time;
• Optimization of kill logic;
• Workflow instance start exception retry;