Tenant settings - Dataphin - Alibaba Cloud Documentation Center

By creating multiple tenants, you can allocate different data units and functional modules to different tenants, ensure data isolation between tenants, and meet the different requirements of different tenants. This topic describes how to create, edit, delete, and restore tenants.

Permission description

Only super administrators and system administrators of the metadata warehouse tenant can create and manage tenants.

Features supported by different engines

Super X

Engine type	X-Coding Assistant	X-O&M Assistant	X-ETL	X-Analysis	X-Asset Q&A	X-Data Steward
MaxCompute	Supported	Supported	Supported	Supported	Supported	Supported
AnalyticDB for PostgreSQL	Supported	Supported	Supported	Supported	Supported	Supported
E-MapReduce3.x	Supported	Supported	Supported	Supported	Supported	Supported
E-MapReduce5.x	Supported	Supported	Supported	Supported	Supported	Supported
CDH5.x	Supported	Supported	Supported	Supported	Supported	Supported
CDH6.x	Supported	Supported	Supported	Supported	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported	Supported	Supported	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported	Supported	Supported	Supported	Supported
AsiaInfo DP5.3	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp TDH 6.x	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp ArgoDB	Supported	Supported	Supported	Supported	Supported	Supported
StarRocks	Supported	Supported	Supported	Supported	Supported	Supported
Lindorm (compute engine)	Supported	Supported	Supported	Supported	Supported	Supported
GaussDB (DWS)	Supported	Supported	Supported	Supported	Supported	Supported
Databricks	Supported	Supported	Supported	Supported	Supported	Supported
Amazon EMR	Supported	Supported	Supported	Supported	Supported	Supported
SelectDB	Supported	Supported	Supported	Supported	Supported	Supported
Doris	Supported	Supported	Supported	Supported	Supported	Supported

Development

Engine type	Intelligent development	Real-time integration	Real-time development	Intelligent operations
MaxCompute	Supported	Supported	Supported	Supported
AnalyticDB for PostgreSQL	Supported	Supported	Supported	Supported
E-MapReduce3.x	Supported	Supported	Supported	Supported
E-MapReduce5.x	Supported	Supported	Supported	Supported
CDH5.x	Supported	Supported	Supported	Supported
CDH6.x	Supported	Supported	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported	Supported	Supported
AsiaInfo DP5.3	Supported	Supported	Supported	Supported
Transwarp TDH 6.x	Supported	Supported	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported	Supported	Supported
Transwarp ArgoDB	Supported	Supported	No	Supported
StarRocks	Supported	Supported	Supported	Supported
Lindorm (compute engine)	Supported	Supported	Supported	Supported
GaussDB (DWS)	No	Supported	Supported	Supported
Databricks	Supported	Supported	Supported	Supported
Amazon EMR	Supported	Supported	Supported	Supported
SelectDB	Supported	Supported	Supported	Supported
Doris	Supported	Supported	Supported	Supported

Administration

Engine type	Data standard	Asset security	Resource administration	Metadata center	Domain asset quality	Global asset quality
MaxCompute	Supported	Supported	Supported	Supported	Supported	Supported
AnalyticDB for PostgreSQL	Supported	Supported	No	Supported	Supported	Supported
E-MapReduce3.x	Supported	Supported	Supported	Supported	Supported	Supported
E-MapReduce5.x	Supported	Supported	Supported	Supported	Supported	Supported
CDH5.x	Supported	Supported	Supported	Supported	Supported	Supported
CDH6.x	Supported	Supported	Supported	Supported	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported	Supported	Supported	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported	Supported	Supported	Supported	Supported
AsiaInfo DP5.3	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp TDH 6.x	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported	Supported	Supported	Supported	Supported
Transwarp ArgoDB	Supported	Supported	No	Supported	Supported	Supported
StarRocks	Supported	Supported	No	Supported	Supported	Supported
Lindorm (compute engine)	Supported	Supported	No	Supported	Supported	Supported
GaussDB (DWS)	Supported	Supported	No	Supported	Supported	Supported
Databricks	Supported	Supported	No	Supported	Supported	Supported
Amazon EMR	Supported	Supported	No	Supported	Supported	Supported
SelectDB	Supported	Supported	No	Supported	Supported	Supported
Doris	Supported	Supported	No	Supported	Supported	Supported

Asset

Engine type	Asset operations	Asset consumption
MaxCompute	Supported	Supported
AnalyticDB for PostgreSQL	Supported	Supported
E-MapReduce3.x	Supported	Supported
E-MapReduce5.x	Supported	Supported
CDH5.x	Supported	Supported
CDH6.x	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported
AsiaInfo DP5.3	Supported	Supported
Transwarp TDH 6.x	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported
Transwarp ArgoDB	Supported	Supported
StarRocks	Supported	Supported
Lindorm (compute engine)	Supported	Supported
GaussDB (DWS)	Supported	Supported
Databricks	Supported	Supported
Amazon EMR	Supported	Supported
SelectDB	Supported	Supported
Doris	Supported	Supported

Application

Engine type	Data service	Offline tag platform	Real-time tag platform	Tag platform audience group selection
MaxCompute	Supported	Supported	Supported	Supported
AnalyticDB for PostgreSQL	Supported	No	No	No
E-MapReduce3.x	Supported	Supported	Supported	Supported
E-MapReduce5.x	Supported	Supported	Supported	Supported
CDH5.x	Supported	Supported	Supported	Supported
CDH6.x	Supported	Supported	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported	Supported	Supported
AsiaInfo DP5.3	Supported	No	No	No
Transwarp TDH 6.x	Supported	Supported	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported	Supported	Supported
Transwarp ArgoDB	Supported	Supported	Supported	Supported
StarRocks	Supported	No	No	No
Lindorm (compute engine)	Supported	Supported	Supported	Supported
GaussDB (DWS)	Supported	No	No	No
Databricks	Supported	No	No	No
Amazon EMR	Supported	No	No	No
SelectDB	Supported	No	No	No
Doris	Supported	No	No	No

Platform

Engine type	Cross-tenant publishing	Row-level permission
MaxCompute	Supported	Supported
AnalyticDB for PostgreSQL	Supported	Supported
E-MapReduce3.x	Supported	Supported
E-MapReduce5.x	Supported	Supported
CDH5.x	Supported	Supported
CDH6.x	Supported	Supported
Cloudera Data Platform 7.x	Supported	Supported
Huawei FusionInsight 8.x	Supported	Supported
AsiaInfo DP5.3	Supported	Supported
Transwarp TDH 6.x	Supported	Supported
Transwarp TDH 9.3.x	Supported	Supported
Transwarp ArgoDB	Supported	Supported
StarRocks	Supported	Supported
Lindorm (compute engine)	Supported	Supported
GaussDB (DWS)	Supported	Supported
Databricks	Supported	Supported
Amazon EMR	Supported	Supported
SelectDB	Supported	Supported
Doris	Supported	Supported

Resource usage description

The total number of processing unit specifications and quality rules depends on the data processing units (DPUs) and rule quotas that you purchase. For more information, see View resource usage.

Create a tenant

Log on to the metadata warehouse tenant as a super administrator or system administrator.
In the top navigation bar of the Dataphin homepage, choose Management Center > System Settings.
In the navigation pane on the left, choose System Settings > Tenant Settings.
On the Tenant Settings page, click Add Tenant to open the Create Tenant dialog box.

In the Create Tenant dialog box, configure the following parameters.

Parameter		Description
Basic Information	Tenant Name	Customize the tenant name. The name cannot exceed 128 characters.
Basic Information	Super Administrator	You can select the super administrator for the target tenant. Note After a tenant is created, the super administrator cannot be changed. If you select Hide Super Administrator And System Administrator, the member information will be displayed as administrator, but the operations that the member with this role can perform are not affected.
Feature Settings	Engine Type	Preselect the offline compute engine needed for the current tenant. Different engines support different features. For more information, see Features supported by different engines. After selecting the engine type, you can select the features that the current tenant can use in the feature area below. Data Processing Unit: Set the number of data processing unit configurations. The DPU quota must be greater than 0 but cannot exceed the remaining processing units. Rule Quota: Domain quality rules and global quality rules share this quota, which only counts the number of quality rules that are in effect. The upper left corner of the tenant list displays the total number of purchased DPUs, quality rules, and the allocated amount. Note The engine type selected here does not affect the engine types that users can select in the tenant. Multi-engine tenants do not support configuring engine types. The feature area includes all features supported by this tenant type by default. Each tenant can create one consumption channel by default, which can be increased by purchasing. You can create data source monitoring rules by enabling either domain quality or global quality. If you purchase both global quality rules and domain quality rules, data source quality rules are counted as domain rules. If you only enable global quality rules, they are counted as global rules. You need to enable intelligent development to use X-ETL. You need to enable asset operations to use X-Analysis/X-Asset Q&A/X-Data Steward.
Schedule Resource Settings	CPU/Memory Allocable Resources	Note This section only allocates scheduling resources for the default Dataphin cluster. The lower limit represents the guaranteed resources for the current tenant. When each tenant needs resources that exceed the lower limit to run tasks, all tenants will first obtain the lower limit quota that is set. The lower limit quota of resources that are not used by this tenant can be borrowed by other tenants. However, when this tenant needs to use the resources, it can reclaim the borrowed resources by waiting in a queue. This tenant can also borrow unused resource quotas from other tenants. However, the total amount of resources that can be used after borrowing cannot exceed the upper limit that is set. Enter the Lower Limit and Upper Limit for CPU and Memory. Lower Limit: You can only enter a value >=0 with one decimal place, and the value cannot exceed the remaining allocable resources. The sum of the lower limits of resources available to all tenants cannot exceed 100%. Upper Limit: You can only enter a value >=0 with one decimal place, and the value must be greater than or equal to the lower limit and less than 100%.
Schedule Resource Settings	Metadata Processing Resource Group	Metadata acquisition tasks are split into multiple subtasks: The process of obtaining initial metadata from the data source and storing it in the Metadata Center to initialize the specified project will use the scheduling resource group specified by the acquisition task to ensure network connectivity. Subsequent processing tasks and data backflow tasks will uniformly use the scheduling resource group configured here to reduce the impact on other task resources. It is recommended to use the resource group of the Dataphin cluster. Note When the CPU or memory configuration in the scheduling resources is not 0, you can select the default resource group of the current tenant. After modifying the resource group configuration, you need to wait about 10 minutes for it to take effect. The resource group of acquisition instances generated before the modification will not be changed accordingly.

Click OK to complete the tenant addition.

Manage tenants

After adding a tenant, you can edit, delete, and restore deleted tenants on the Tenant Settings page.

Section

Description

①Tenant List

Displays the Tenant Name/ID, Super Administrator, Used Quota of DPUs/quality rules, Total Quota, Resource Range Settings, Current Resource Usage, and Functional Modules information.

Resource Range Settings: The lower and upper limits set in the scheduling resource settings, not the actual usage values.
Current Resource Usage: The amount of resources allocated to the corresponding tenant up to the time the interface is refreshed, which is the actual resource usage of the current tenant.

②Operation Area

You can perform Edit, Delete, and Restore operations on tenants.

When the tenant status is Creating, no operations are supported. When the tenant status is Updating, edit and delete operations are not supported. When the tenant status is Creation Failed or Update Failed, you can re-edit the tenant. After re-editing, a tenant with update failure will be re-initialized.

Note

Resources such as DPUs, scheduling resources, and quality rule resources are deducted in advance for tenants that are being created. If the creation fails, the deducted resources will be returned.

Edit: You can edit the tenant name, DPU quota, and functional modules. Engine type editing is not supported. You can set the lower and upper limits of CPU and memory for the metadata warehouse tenant.
There are the following limitations for downgrading features:
- If the tenant already contains intelligent development-related objects (business units, business objects, data domains, business activities, logical tables, business filters, atomic metrics, derived metrics, etc.), you cannot cancel intelligent development. You need to delete the target objects first, and then cancel.
- If real-time development tasks, quality rules, data detection rules or data masking rules, data service APIs, etc. have already been configured, you cannot cancel the corresponding functional modules. You need to delete the corresponding configurations first, and then cancel.
  If real-time integration tasks (including draft, development, and production states) are already included, real-time integration cannot be disabled. You need to delete the corresponding tasks first, and then cancel.
  If baselines and throttling rules are already included, intelligent operations cannot be disabled. You need to delete the corresponding baselines and throttling rules first, and then cancel.
- Basic development version cannot be canceled.
Note
If you have enabled the custom resource group feature, you can modify the amount of scheduling resources allocated to the metadata warehouse tenant. Please note that if the resources allocated to the metadata warehouse tenant are too few, it may cause system task production delays, which may affect the display of some page features (such as field heat and other information on the directory page) and data updates of the metadata sharing model.
Delete: Select the tenant to be deleted, and click the Actions column of the target tenant, click the Delete icon. In the Delete Tenant dialog box, enter the 6-digit verification code and click OK.
Note
- The metadata warehouse tenant cannot be deleted.
- After a tenant is deleted, it remains in the tenant list for 30 days, during which time the tenant can be restored. After 30 days, the deleted tenant will be removed from the tenant list. The tenant data will not be deleted. To delete it completely, contact technical support personnel.
- If custom resource groups have been configured for the current tenant, please delete the custom resource groups first before deleting the tenant.
Restore: Select the tenant to be restored, and in the Restore Tenant dialog box, click OK.
If your tenant does not support restoration, the possible reasons include the following situations:
- The number of used DPUs is greater than the remaining allocable DPUs.
- The number of used quality rules is greater than the remaining allocable quality rules.
- There is a downgrade in tenant features.
- The scheduling resources (CPU or memory) configured for the tenant exceed the maximum remaining amount that the system can allocate.