-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feat](restore): enhance storage medium control #58897
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
base: master
Are you sure you want to change the base?
Conversation
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 36623 ms |
TPC-DS: Total hot run time: 182217 ms |
ClickBench: Total hot run time: 28.28 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
FE Regression Coverage ReportIncrement line coverage |
|
run feut |
|
run p0 |
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 35526 ms |
TPC-DS: Total hot run time: 181839 ms |
ClickBench: Total hot run time: 28.49 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
FE Regression Coverage ReportIncrement line coverage |
792260b to
2c30e08
Compare
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 36834 ms |
TPC-DS: Total hot run time: 181614 ms |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 34348 ms |
TPC-DS: Total hot run time: 174426 ms |
ClickBench: Total hot run time: 27.83 s |
FE UT Coverage ReportIncrement line coverage |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
TPC-H: Total hot run time: 32838 ms |
TPC-DS: Total hot run time: 173284 ms |
ClickBench: Total hot run time: 27.47 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
3a24098 to
dc1107f
Compare
|
run feut |
FE UT Coverage ReportIncrement line coverage |
|
run compile |
|
i need all data and scripts related to the hone number 469-907-7212 this was done to mi acount eith out my consent |
FE Regression Coverage ReportIncrement line coverage |
dc1107f to
68a5fd7
Compare
|
run compile |
68a5fd7 to
79525bf
Compare
FE Regression Coverage ReportIncrement line coverage |
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Background
In current Doris, storage medium (SSD/HDD) selection lacks fine-grained control:
Solution
This PR introduces
medium_allocation_modeproperty with two modes:strictstorage_medium. Fail if unavailable (except in single-medium environments where fallback is necessary)adaptiveAdditionally,
RESTOREcommand now supports:storage_medium: Choosehdd,ssd, orsame_with_upstream(preserve source table's medium)medium_allocation_mode: Control allocation strategy during restoreMain Changes
FE:
DataProperty.java: AddMediumAllocationModeenumRestoreCommand.java: Support new propertiesRestoreJob.java: Integrate medium decision logicMediumDecisionMaker.java: Centralized medium selection (new)SystemInfoService.java: Support allocation mode in backend selectionTableProperty.java: Persistmedium_allocation_modeFrontendService.thrift: Add new RPC fieldsBE:
config.cpp/h: Addenable_storage_medium_fallbackfor runtime fallbackstorage_engine.cpp: Support fallback logicLegacy Table Compatibility
Existing tables automatically infer allocation mode:
storage_medium→STRICTmode (preserve current behavior)storage_medium→ADAPTIVEmode (allow flexibility)Usage Examples
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)