Limits
This topic describes the limits of Self-managed MyBase.
When you use Self-managed MyBase, specific unexpected operations may result in unstable or unavailable databases. To prevent this issue, take note of the limits of Self-managed MyBase.
Prohibited operation | Possible result | Suggestion |
Delete host nodes of ApsaraDB for MyBase in the Elastic Compute Service (ECS) console. | Data loss occurs and ApsaraDB for MyBase clusters become unavailable. | None. |
Delete the Container Service for Kubernetes (ACK) cluster or node pool on which ApsaraDB for MyBase is deployed in the ACK console. | Data loss occurs and ApsaraDB for MyBase clusters become unavailable. | None. |
Modify parameters in component configuration files in the ECS console. | After ApsaraDB for MyBase restarts, the modified parameters are overwritten. | Modify the parameters in the ApsaraDB for MyBase console. |
Redeploy ECS instances in the ECS console. | The usage of ApsaraDB for MyBase clusters is affected. | None. |
Attach disks to the host nodes of ApsaraDB for MyBase in the ECS console. | The disks become unavailable because ApsaraDB for MyBase cannot recognize and initialize the disks. | None. |
Detach disks from the host nodes of ApsaraDB for MyBase in the ECS console. | Data loss occurs because ApsaraDB for MyBase is unaware of the disk detaching operation. | |
Modify the security group to which ECS instances belong when an ApsaraDB for MyBase cluster or instance is running. |
| None. |