Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Hotfix][Zeta] Fix zeta scheduler bug #6050

Merged
merged 8 commits into from
Dec 26, 2023

Conversation

EricJoy2048
Copy link
Member

Purpose of this pull request

  1. Fix the scheduler bug when slot is not enough.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Already add test case.

Check list

@EricJoy2048 EricJoy2048 force-pushed the 163_fix_zeta_scheduler_bug branch from 4337977 to 13d03a0 Compare December 21, 2023 05:12
@EricJoy2048 EricJoy2048 force-pushed the 163_fix_zeta_scheduler_bug branch from 284323c to 499f464 Compare December 23, 2023 06:08
Comment on lines -120 to -123
if (StringUtils.isNotEmpty(jobResult.getError())
|| jobResult.getStatus().equals(JobStatus.FAILED)) {
throw new SeaTunnelEngineException(jobResult.getError());
}
Copy link
Member

Choose a reason for hiding this comment

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

If client never throw exception even job failed. The shell status code always return 0, does not meet shell standards. Also client side will not get job result error msg. We need test case to cover it.

Copy link
Member Author

Choose a reason for hiding this comment

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

If client never throw exception even job failed. The shell status code always return 0, does not meet shell standards. Also client side will not get job result error msg. We need test case to cover it.

Done, I have added test cases.

@EricJoy2048 EricJoy2048 force-pushed the 163_fix_zeta_scheduler_bug branch from 754f56f to f246365 Compare December 25, 2023 05:35
@hailin0 hailin0 merged commit 5ff4395 into apache:dev Dec 26, 2023
4 checks passed
alextinng pushed a commit to alextinng/seatunnel that referenced this pull request Jan 4, 2024
alextinng pushed a commit to alextinng/seatunnel that referenced this pull request Jan 4, 2024
chaorongzhi pushed a commit to chaorongzhi/seatunnel that referenced this pull request Aug 21, 2024
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.

3 participants