Skip to content

Conversation

@reele
Copy link
Contributor

@reele reele commented Apr 4, 2025

fix #17109

Brief change log

add sethost in RecoverFailureTaskCommandHandler and WorkflowFailoverCommandHandler

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:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

@SbloodyS SbloodyS added the bug Something isn't working label Apr 4, 2025
@SbloodyS SbloodyS added this to the 3.3.1 milestone Apr 4, 2025
Copy link
Contributor

@yingh0ng yingh0ng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

ruanwenjun
ruanwenjun previously approved these changes Apr 8, 2025
Copy link
Member

@ruanwenjun ruanwenjun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, good catch.

} catch (ServiceException e) {
throw e;
} catch (Exception e) {
log.error("WorkflowInstance stop failed, workflowInstanceId: {}, workflowInstanceName: {}", workflowInstance.getId(), workflowInstance.getName(), e);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove this log? Since the exception stack will be logged by aspect.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the following ServiceException didn't contain the original call stack, it won't print to api log, so i added this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not a good way, i'll remove it first.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I got you, since ServiceException are seems as expected exception, although it contains the origin stack, but will not log, so we need to change the aspect code to log the exception stack.

@ruanwenjun
Copy link
Member

Please fix the code style.

@reele
Copy link
Contributor Author

reele commented Apr 9, 2025

Please fix the code style.

fixed

@ruanwenjun ruanwenjun requested a review from SbloodyS April 9, 2025 14:11
Copy link
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@ruanwenjun ruanwenjun force-pushed the fix-recovered-workflow-host-may-incorrect branch from 78ff9ac to 7fca832 Compare April 10, 2025 15:11
@sonarqubecloud
Copy link

@SbloodyS SbloodyS merged commit 66c1d87 into apache:dev Apr 11, 2025
70 checks passed
davidzollo pushed a commit to davidzollo/dolphinscheduler that referenced this pull request Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] [AbstractCommandHandler] Workflow's host may incorrect after recover, cause api operation failed.

4 participants