Note
This parameter is available starting with V2.2.50.
Description
enable_sys_unit_standalone specifies whether to allow the system tenant's unit to be exclusive to a server.
Privilege requirements
Query the parameter
The
systenant and all user tenants can use theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview to query this parameter.Modify the parameter
Only the
systenant can modify this parameter. User tenants cannot modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Bool |
| Default value | False |
| Value range |
|
| Modifiable | Yes. You can use the ALTER SYSTEM SET statement to modify the parameter. |
| Effective upon OBServer node restart | No. The setting takes effect immediately. |
Considerations
When this parameter is set to True, the following effects will occur:
When you create or increase the number of resource pools, you must consider the system tenant's unit. You cannot deploy the units of a user tenant with the units of the system tenant on the same server.
The system will migrate other units from the server where the system tenant's unit is located.
When you offline or delete a server, the system will first migrate the units of the system tenant and then migrate the units of other tenants. Other tenants' units cannot be deployed with the system tenant's unit on the same server.
During tenant group balancing, the system will filter out the server where the system tenant's unit is located from the available servers in the tenant group. The units of the tenant group will be evenly distributed across the remaining servers.
Examples
Prevent the system tenant's unit from being exclusive to a server.
obclient> ALTER SYSTEM SET enable_sys_unit_standalone = False;