Dataphin:Create a custom resource group

Limits

Each tenant can create up to 100 resource groups, including the tenant default resource group.

Permissions

Custom roles with Manage Resource Settings permission and system roles including super administrator and system administrator can create custom resource groups.

Procedure

1. In the top menu bar on the Dataphin home page, select Management Center > System Settings.

2. In the left-side navigation pane, select Tenant Settings > Resource Settings.

3. Under the Resource Group Configuration tab, click + Create Custom Resource Group.

4. In the Create Custom Resource Group dialog box, configure parameters.

   Parameter	Description
   Resource Group Name	Enter the resource group name. Up to 128 characters are supported.
   Owner	Select the owner of the current resource group. You can enter a username keyword to search.
   Cluster	Select the cluster to which the resource group belongs. You can select Default Cluster or a custom cluster available to the current tenant (that is, a cluster associated with all tenants or specified for the current tenant). Note The cluster cannot be modified after creation.
   Schedule Resource Settings	CPU and Memory: Configure the Upper Limit and Lower Limit for CPU and Memory. When the cluster is selected as Default Cluster: Lower limit: Lower limit = Percentage (%) × Tenant lower limit. You need to enter a percentage number, accurate to one decimal place, and the default is empty. Remaining resources = 1 - the sum of the percentages of the tenant's lower limit already allocated to other resource groups. The lower limit cannot exceed the remaining resources. Upper limit: Upper limit = Percentage (%) × Tenant upper limit. You need to enter a percentage number, accurate to one decimal place, and the default is 100%. The upper limit cannot be lower than the lower limit. When the cluster is selected as Registered External Cluster: Lower limit: Lower limit = Percentage (%) × Total cluster capacity. You need to enter a percentage number, accurate to one decimal place, and the default is empty. Remaining resources = 1 - the sum of the percentages of the total cluster capacity already allocated to other resource groups, where the total cluster capacity is the total capacity of the selected cluster in the above configuration. The lower limit cannot exceed the remaining resources. Upper limit: Upper limit = Percentage (%) × Total cluster capacity. You need to enter a percentage number, accurate to one decimal place, and the default is 100%. The upper limit cannot be lower than the lower limit. Note The lower limit represents the guaranteed resources for the current resource group. When tenant resources are tight, all resource groups are prioritized to obtain the set lower limit quota. The unused lower limit quota of this resource group can be borrowed by other resource groups of the current tenant. However, when this resource group needs to use it, it can be reclaimed through a queuing mechanism. This resource group can also borrow unused resource quotas from other resource groups of the current tenant. However, the total amount of resources available after borrowing cannot exceed the set upper limit. To avoid the lower limit of the resource group exceeding the upper limit due to tenant resource adjustments, the upper limit ratio of all resource groups must be greater than the lower limit. Resource groups can only borrow resources from resource groups within the same cluster. Description: Enter a brief description of the current resource group, not exceeding 1000 characters. Scenario: Includes offline task and real-time task scenarios. Offline tasks: Used to support daily scheduling and batch operations for offline tasks. Batch operations: Resource groups that can be selected for batch operations, such as batch data backfill. The resource group configured for batch operations is only effective for the instances covered by the batch operation. Task daily scheduling: Refers to the resource group used for task trial runs, smoke testing, recurring schedule, and other operations. You need to configure the associated projects that can use the current resource group. After configuration, in the project configuration, you can select the associated resource group as the project default resource group. For more information, see the referenced document. Real-time tasks: After enabling real-time development in tenant settings, support selecting real-time tasks. Real-time task custom resource groups support Dataphin clusters and registered schedule clusters. The created real-time task resource group can be used for Session cluster task testing and real-time task execution. When the scenario is selected as Real-time tasks, CPU/Memory upper and lower limits configuration is not supported. You only need to enter the percentage values for CPU and memory. Session cluster task testing: Used to create a Session cluster for real-time task testing. Note The minimum specification requirement for a Session cluster is 3C 12G. Only one custom resource group with the scenario of Session cluster can be created per tenant. All projects under this tenant share this resource group. Only custom resource groups for real-time tasks can be used to create a Session cluster for real-time task testing. Real-time task execution: Used for computing resource allocation in the Flink on K8s (Kubernetes) deployment mode. Note When the schedule cluster is selected as Non-default Cluster (that is, an externally registered cluster), the real-time task scenario only supports real-time task execution. For the priority of resource group effectiveness, see the referenced document.

5. Click OK to complete the custom resource group configuration.

   The modified configuration of the resource group may take some time to take effect (estimated 5 minutes). Please be patient.