branch-4.1: [feature](cloud) Add table-level event-driven warm up (#63832) by bobhan1 · Pull Request #64602 · apache/doris

bobhan1 · 2026-06-17T05:17:57Z

Proposed changes

Backport #63832 to branch-4.1: add table-level event-driven warm-up support and related FE/BE metrics, parsing, show output, and regression coverage.

This backport also includes a small doris-compose compatibility fix for this branch so the cloud docker regression runner can accept up --env and initialize external_ms_cluster before cloud cluster setup. Without it, the docker suites fail during compose argument handling before product code is exercised.

Validation

git diff HEAD^ HEAD --check
./run-be-ut.sh --clean --run --coverage --filter=CloudWarmUpManagerTest.*:CloudWarmUpManagerFilterTest.*:MBvarWindowedAdderTest.* -j100
./run-fe-ut.sh --run org.apache.doris.cloud.CacheHotspotManagerTableFilterTest,org.apache.doris.cloud.CloudWarmUpJobTableFilterTest,org.apache.doris.cloud.OnTablesFilterTest,org.apache.doris.cloud.WarmUpClusterOnTablesParseTest,org.apache.doris.cloud.WarmUpStatsTest,org.apache.doris.cloud.catalog.CloudInstanceStatusCheckerTest,org.apache.doris.metric.MetricsTest
./build.sh --be --fe --cloud -j100
docker build -f docker/runtime/doris-compose/Dockerfile -t bh-cluster-2 .
DORIS_FDB_IMAGE=foundationdb/foundationdb:7.1.26-single-layer ./run-regression-test.sh --run -d regression-test/suites/cloud_p0/cache/multi_cluster/warm_up/on_tables -runMode=cloud -dockerSuiteParallel 1 -image bh-cluster-2
- Result: Test 19 suites, failed 0 suites, fatal 0 scripts, skipped 0 scripts

hello-stephen · 2026-06-17T05:18:02Z

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

bobhan1 · 2026-06-17T06:15:11Z

run buildall

hello-stephen · 2026-06-17T10:25:51Z

BE Regression && UT Coverage Report

Increment line coverage 39.75% (161/405) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	73.77% (27438/37196)
Line Coverage	57.35% (297149/518091)
Region Coverage	55.15% (250169/453580)
Branch Coverage	56.46% (108141/191526)

Issue Number: None Problem Summary: This PR adds table-level event-driven cloud warm-up support and improves active incremental warm-up progress observability. Before this change, event-driven warm-up was only controlled at compute-group granularity. Once a load-event warm-up job was enabled for a source and target compute group pair, all source-side table writes could trigger warm-up to the target compute group. That is inefficient for workloads where only selected core tables, high-frequency query tables, or selected async materialized views need to stay warm. This PR lets users define the warm-up scope with `ON TABLES` when creating an event-driven load warm-up job. FE persists the normalized table filter in the warm-up job, resolves matched table ids dynamically, sends the table ids to BE, and lets BE filter warm-up rowsets by table id. User-visible behavior: - `WARM UP ... ON TABLES` supports table-level event-driven warm-up. - Table filters support `INCLUDE` and `EXCLUDE` rules. - Rules support `*` and `?` wildcards, for example `db.table`, `db.*`, `*.orders_*`, and `log_db.log_?`. - `INCLUDE` defines the candidate warm-up scope, and `EXCLUDE` removes tables from that included scope. - Rules are canonicalized before duplicate checks, so semantically equivalent filters do not create duplicate jobs just because rule order differs. - Matching covers both regular OLAP tables and async materialized views. - Matched table ids are refreshed as tables or async materialized views are created, dropped, or renamed. - The same source compute group can create independent table-level warm-up jobs to different target compute groups with different table filters. - `SHOW WARM UP JOB` exposes the table-level job type, table filter, matched tables, and SyncStats. - `SHOW WARM UP JOB` list output keeps compact SyncStats, while single-job lookup keeps detailed windowed SyncStats. Example: ```sql WARM UP COMPUTE GROUP query_cg WITH COMPUTE GROUP write_cg ON TABLES ( INCLUDE 'core_db.config', INCLUDE 'report_db.monthly_*', INCLUDE '*.sales_*', EXCLUDE '*.*_archive' ) PROPERTIES ( "sync_mode" = "event_driven", "sync_event" = "load" ); ``` Conflict and virtual compute group behavior: - Table-level load-event warm-up and cluster-level load-event warm-up are mutually exclusive for the same source and target compute group pair. - If a conflicting job already exists, creation returns an error that includes the conflicting job id; table-level conflicts also include the table filter. - Duplicate checks within the same job type still follow the existing duplicate-check logic. - VCG-managed cluster-level load-event warm-up creation does not fail on conflict. Because VCG jobs are created by the MS HTTP API path, FE cancels existing table-level load-event warm-up jobs with the same source and target first, then recreates the VCG-managed cluster-level job. - Manually creating a table-level load-event warm-up job is rejected only when both source and target compute groups are owned by the same VCG. - SQL still cannot use a virtual compute group directly as the source or target compute group. Warm-up progress observation: - BE records per-job windowed requested, finished, and failed warm-up statistics. - BE exposes per-job warm-up statistics through `/api/warmup_event_driven_stats`. - FE aggregates BE statistics and caches the aggregated result in the warm-up job. - SyncStats includes source-side and target-side warm-up size/count progress across windows. - SyncStats includes trigger-time progress, so users can observe whether the target compute group is behind the latest source-side warm-up trigger. - FE `/metrics` exposes per-job active warm-up metadata, synchronized size, and trigger gap metrics for cloud event-driven warm-up jobs. Support table-level event-driven cloud warm-up with `ON TABLES` filters and per-job warm-up sync statistics. - Test - [x] Regression test - [x] Unit Test - [x] Manual test - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason - Behavior changed: - [ ] No. - [x] Yes. `WARM UP` supports table-level `ON TABLES` filters for event-driven load warm-up, and warm-up job output/metrics expose table filter, matched tables, SyncStats, and trigger-gap information. - Does this need documentation? - [ ] No. - [x] Yes. apache/doris-website#3829

bobhan1 · 2026-06-18T09:04:19Z

run buildall

hello-stephen · 2026-06-18T09:34:22Z

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	77.24% (1877/2430)
Line Coverage	64.28% (33720/52455)
Region Coverage	64.76% (17365/26814)
Branch Coverage	53.90% (9279/17216)

hello-stephen · 2026-06-18T12:09:58Z

BE UT Coverage Report

Increment line coverage 39.61% (162/409) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	54.14% (20612/38073)
Line Coverage	37.70% (196312/520749)
Region Coverage	34.08% (153583/450598)
Branch Coverage	35.01% (66974/191284)

hello-stephen · 2026-06-18T14:09:37Z

BE Regression && UT Coverage Report

Increment line coverage 39.75% (161/405) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	73.77% (27445/37203)
Line Coverage	57.40% (297481/518246)
Region Coverage	55.10% (249973/453703)
Branch Coverage	56.48% (108204/191578)

hello-stephen · 2026-06-18T14:26:08Z

FE Regression Coverage Report

Increment line coverage 4.18% (36/862) 🎉
Increment coverage report
Complete coverage report

bobhan1 force-pushed the branch-4.1-pick-63832 branch 2 times, most recently from 62c994a to 66f4060Compare June 17, 2026 06:04

bobhan1 marked this pull request as ready for review June 17, 2026 06:04

bobhan1 requested a review from yiguolei as a code owner June 17, 2026 06:04

bobhan1 changed the title ~~[branch-4.1][feature](cloud) Add table-level event-driven warm up (#63832)~~branch-4.1: [feature](cloud) Add table-level event-driven warm up (#63832)Jun 17, 2026

bobhan1 force-pushed the branch-4.1-pick-63832 branch from 66f4060 to 8f2a3e6Compare June 18, 2026 09:02

yiguolei approved these changes Jun 22, 2026
View reviewed changes

yiguolei merged commit b4e8449 into apache:branch-4.1Jun 22, 2026
27 of 31 checks passed

Navigation Menu

Uh oh!

branch-4.1: [feature](cloud) Add table-level event-driven warm up (#63832) - #64602

branch-4.1: [feature](cloud) Add table-level event-driven warm up (#63832)#64602
yiguolei merged 1 commit into
apache:branch-4.1from
bobhan1:branch-4.1-pick-63832

bobhan1 commented Jun 17, 2026

Uh oh!

hello-stephen commented Jun 17, 2026

Uh oh!

bobhan1 commented Jun 17, 2026

Uh oh!

hello-stephen commented Jun 17, 2026

Uh oh!

bobhan1 commented Jun 18, 2026

Uh oh!

hello-stephen commented Jun 18, 2026

Uh oh!

hello-stephen commented Jun 18, 2026

Uh oh!

hello-stephen commented Jun 18, 2026

Uh oh!

hello-stephen commented Jun 18, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

bobhan1 commented Jun 17, 2026

Proposed changes

Validation

Uh oh!

hello-stephen commented Jun 17, 2026

Uh oh!

bobhan1 commented Jun 17, 2026

Uh oh!

hello-stephen commented Jun 17, 2026

BE Regression && UT Coverage Report

Uh oh!

bobhan1 commented Jun 18, 2026

Uh oh!

hello-stephen commented Jun 18, 2026

Cloud UT Coverage Report

Uh oh!

hello-stephen commented Jun 18, 2026

BE UT Coverage Report

Uh oh!

hello-stephen commented Jun 18, 2026

BE Regression && UT Coverage Report

Uh oh!

hello-stephen commented Jun 18, 2026

FE Regression Coverage Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants