This is an automated email from the ASF dual-hosted git repository.

kassiez pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new e642063357b Update typo of workload management (#2844)
e642063357b is described below

commit e642063357b5852f6169c636af5849a11a24aac9
Author: KassieZ <[email protected]>
AuthorDate: Fri Sep 5 12:27:07 2025 +0800

    Update typo of workload management (#2844)
    
    ## Versions
    
    - [ ] dev
    - [ ] 3.0
    - [ ] 2.1
    - [ ] 2.0
    
    ## Languages
    
    - [ ] Chinese
    - [ ] English
    
    ## Docs Checklist
    
    - [ ] Checked by AI
    - [ ] Test Cases Built
---
 .../workload-management/workload-group-bind-compute-group.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/docs/admin-manual/workload-management/workload-group-bind-compute-group.md 
b/docs/admin-manual/workload-management/workload-group-bind-compute-group.md
index fa2b1153408..5500d7798e2 100644
--- a/docs/admin-manual/workload-management/workload-group-bind-compute-group.md
+++ b/docs/admin-manual/workload-management/workload-group-bind-compute-group.md
@@ -5,7 +5,7 @@
 }
 ---
 
-## 背景
+## Background
 Doris supports logical partitioning of BE (Backend) resources within a cluster 
through the Compute Group feature, forming independent sub-cluster units to 
achieve physical isolation of computing and storage resources for different 
business parties. Due to the significant differences in load characteristics 
among business parties, their configuration requirements for Workload Groups 
often exhibit obvious distinctions.
 
 In early versions, the Workload Groups configured by users would take effect 
globally across all Compute Groups, forcing different business parties to share 
the same set of Workload Group configurations. For example, Business A’s 
high-concurrency queries and Business B’s large-scale data analysis might 
require completely different resource quotas, but the old architecture could 
not meet such differentiated needs, limiting the flexibility of resource 
management.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to