Note
For V2.2.50, this parameter is available starting with V2.2.50.
Description
enable_sys_unit_standalone specifies whether to allow the system tenant unit to run on a standalone node.
Privilege requirements
Query the parameter
The
systenant and all user tenants can query this parameter by using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.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
If you set this parameter to True, the following effects occur:
When you create or increase the number of resource pools, you must consider the system tenant unit. You cannot deploy the system tenant unit and the user tenant units on the same server.
The system automatically migrates other units that are deployed on the same server as the system tenant unit.
When you offline or delete a server, the system automatically migrates the system tenant unit first and then other tenant units. The other tenant units cannot be deployed on the same server as the system tenant unit.
During tenant group balancing, the system automatically filters out the server that hosts the system tenant unit from the available servers for tenant groups. The tenant group units are evenly distributed across the servers except the one that hosts the system tenant unit.
Examples
Prevent the system tenant unit from running on a standalone node.
obclient> ALTER SYSTEM SET enable_sys_unit_standalone = False;