-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](cloud) Exposes cloud balance metrics #57200
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
ClickBench: Total hot run time: 28.37 s |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
run p0 |
|
run nonConcurrent |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
FE Regression Coverage ReportIncrement line coverage |
1 similar comment
FE Regression Coverage ReportIncrement line coverage |
Exposes cloud balance related metrics to show whether the compute group is performing balance scheduling. When `*_balance_num` metrics are all 0, the current compute group is considered to be in a balanced state. Note: These metrics are valid only when requesting the fe master (balance scheduling is performed on the fe master) ``` curl "http://175.42.1.1:8030/metrics" |rg '_balance_num' # HELP doris_fe_cloud_table_balance_num current cluster cloud table balance sync edit log number # TYPE doris_fe_cloud_table_balance_num counter doris_fe_cloud_table_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 5 doris_fe_cloud_table_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_partition_balance_num current cluster cloud partition balance sync edit log number # TYPE doris_fe_cloud_partition_balance_num counter doris_fe_cloud_partition_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_partition_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_smooth_upgrade_balance_num current cluster cloud smooth upgrade sync edit log number # TYPE doris_fe_cloud_smooth_upgrade_balance_num counter doris_fe_cloud_smooth_upgrade_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_smooth_upgrade_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_global_balance_num current cluster cloud be balance sync edit log number # TYPE doris_fe_cloud_global_balance_num counter doris_fe_cloud_global_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_global_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_warm_up_balance_num current cluster cloud warm up cache sync edit log number # TYPE doris_fe_cloud_warm_up_balance_num counter doris_fe_cloud_warm_up_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_warm_up_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 ```
Exposes cloud balance related metrics to show whether the compute group is performing balance scheduling. When `*_balance_num` metrics are all 0, the current compute group is considered to be in a balanced state. Note: These metrics are valid only when requesting the fe master (balance scheduling is performed on the fe master) ``` curl "http://175.42.1.1:8030/metrics" |rg '_balance_num' # HELP doris_fe_cloud_table_balance_num current cluster cloud table balance sync edit log number # TYPE doris_fe_cloud_table_balance_num counter doris_fe_cloud_table_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 5 doris_fe_cloud_table_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_partition_balance_num current cluster cloud partition balance sync edit log number # TYPE doris_fe_cloud_partition_balance_num counter doris_fe_cloud_partition_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_partition_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_smooth_upgrade_balance_num current cluster cloud smooth upgrade sync edit log number # TYPE doris_fe_cloud_smooth_upgrade_balance_num counter doris_fe_cloud_smooth_upgrade_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_smooth_upgrade_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_global_balance_num current cluster cloud be balance sync edit log number # TYPE doris_fe_cloud_global_balance_num counter doris_fe_cloud_global_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_global_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 # HELP doris_fe_cloud_warm_up_balance_num current cluster cloud warm up cache sync edit log number # TYPE doris_fe_cloud_warm_up_balance_num counter doris_fe_cloud_warm_up_balance_num{cluster_id="compute_cluster_id", cluster_name="compute_cluster"} 0 doris_fe_cloud_warm_up_balance_num{cluster_id="other_cluster_id", cluster_name="other_cluster"} 0 ```
What problem does this PR solve?
Exposes cloud balance related metrics to show whether the compute group is performing balance scheduling. When
*_balance_nummetrics are all 0, the current compute group is considered to be in a balanced state.Note: These metrics are valid only when requesting the fe master (balance scheduling is performed on the fe master)
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)