bobhan1 opened a new pull request, #67643:
URL: https://github.com/apache/doris/pull/67643
### What problem does this PR solve?
Issue Number: None
Related PR: #67527
Backport #67527 to branch-4.1 (cherry-picked from
94ad62a4aeaefbb3f41336f50fa0ecf8b4cdf203).
Cloud warm-up jobs can remain pending when the worker pool is saturated.
This change reserves active slots before submission, retries rejected jobs,
prioritizes least-recently-scheduled jobs, and applies mutable concurrency and
scheduler interval settings.
The only cherry-pick conflict was in ConfigTest; retain the branch-4.1 tests
and add the scheduler interval validation test.
### Release note
Fix cloud warm-up jobs remaining pending when the scheduler thread pool is
saturated.
### Validation
- Passed: `git diff --check upstream/branch-4.1...HEAD`.
- Attempted: `./run-fe-ut.sh --run
org.apache.doris.common.ConfigTest,org.apache.doris.cloud.CacheHotspotManagerSchedulerTest`.
- Local validation blocked before test execution: fe-common compilation
fails in generated Thrift Java sources with `cannot find symbol: class
Generated` in `javax.annotation`. Neither selected test class ran.
### Check List (For Author)
- Test
- [ ] Regression test
- [x] Unit Test (included; local execution blocked as described above)
- [ ] Manual test
- [ ] No need to test or manual test
- Behavior changed:
- [ ] No.
- [x] Yes. Runnable warm-up jobs are scheduled fairly and rejected
submissions are retried.
- Does this need documentation?
- [x] No.
- [ ] Yes.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
