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 be deployed on a standalone server.
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
When this parameter is set to True, the following effects occur:
When you create or add a resource pool, you must consider the system tenant unit. You cannot deploy the system tenant unit and a user tenant unit 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 first migrates the system tenant unit, and then migrates other tenant units. Other tenant units cannot be deployed on the same server as the system tenant unit.
When you perform tenant group balancing, the system excludes 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
Set the system tenant unit to be deployed on a standalone server.
obclient> ALTER SYSTEM SET enable_sys_unit_standalone = False;