ob_tenant_log_disk_usage_high OceanBase tenant log disk usage exceeded the limit

Description

In OceanBase Database V4.0 and later, the log disk space of a tenant is isolated from that of other tenants. Each server reserves sufficient log disk space for each tenant to prevent tenants from affecting each other. The LOG_DISK_SIZE parameter is added to unit configs to specify the log disk size of each unit. If you do not specify the LOG_DISK_SIZE parameter, the value of the MIN_MEMORY parameter is used by default.

When you create or migrate a unit of a tenant, Root Service selects a server whose remaining log disk space is larger than the value of the LOG_DISK_SIZE parameter as the target server. This alert is triggered when the log disk usage of a tenant exceeds the specified threshold.

Principle

Alert rule

Alert information

Alert templates

• Alert overview
  • Template: ${alarm_target} ${alarm_name}
  • Example: ob_cluster=C1-1000:tenant_name=T1 OceanBase tenant log disk usage exceeds the threshold.
• Alert details
  • Template: Cluster: ${ob_cluster_name}. Zone: ${obzone}. Tenant: ${tenant_name}. Alert: OceanBase tenant log disk usage reaches ${value_shown}, which exceeds the threshold of ${alarm_threshold} %.
  • Example: Cluster: C1. Zone: Z1. Tenant: T1. Alert: OceanBase tenant log disk usage reaches 96 %, which exceeds the threshold of 95 %.
• Alert restored
  • Template: Alert: ${alarm_name}. OceanBase tenant log disk usage: ${value_shown}
  • Example: Alert: OceanBase tenant log disk usage exceeds the threshold. OceanBase tenant log disk usage: 90 %.

Impact on the system

When the free space of the OBServer log disk is insufficient, OBServer cannot work properly.

Possible causes

Improper log disk settings.

Solutions

OceanBase Database V4.0 provides the following log disk parameters:

• log_disk_size: the total log disk space that the server can use. The default value is 0, which indicates that the log disk space available for the server is calculated based on the actual space of the local log disk.

• log_disk_percentage: the usage of the log disk in percentage. If you set the log_disk_size parameter to 0, the log disk space is allocated based on the value of the log_disk_percentage parameter. The default value is 0, which indicates that calculations are automatically performed based on whether logs and data share the same disk.

If you set the log_disk_size and datafile_size parameters to 0, the sizes of the log disk and data disk are automatically calculated by using the following methods:

1. If the value of the log_disk_percentage or datafile_disk_percentage parameter is not 0, the following formulas are used:

   1. log_disk_size = Size of the physical disk where logs are stored × log_disk_percentage

   2. datafile_size = Size of the physical disk where data is stored × datafile_disk_percentage

2. If the log_disk_percentage or datafile_disk_percentage parameter is set to 0, the following settings prevail and the sizes of the log disk and data disk are calculated based on the following settings:

   1. If data and logs share a disk:

      1. log_disk_percentage = 30%

      2. datafile_disk_percentage = 60%

   2. When data and logs do not share one disk and each has exclusive disks:

      1. log_disk_percentage = 90%

      2. datafile_disk_percentage = 90%

3. If data and logs share a disk, you can adjust the default value of the log_disk_percentage parameter to avoid insufficient log disk space.

4. If data and logs do not share a disk, the log disk has ample space, you can set the log_disk_percentage parameter to an appropriately larger value.