Insufficient disk space (error code -4290)
In OceanBase Database V3.x and earlier versions, the log disk must be deployed independently and exclusively. Starting from OceanBase Database V4.0, the log and other files can be stored together, and the user needs to configure the specific size of the log disk. OceanBase Database will pre-allocate the disk space for the data disk and CLOG disk when the OBServer starts based on the user's configuration.
Therefore, the configuration items log_disk_size and log_disk_percentage are introduced, and they need to be used together.
log_disk_size: The size of the log disk, which is the total available space for the log disk on this OBServer. The default value is 0, indicating that the space should be calculated based on the actual space of the local log disk (compatible with the behavior of OceanBase Database V3.x).log_disk_percentage: The percentage of the log disk space. Whenlog_disk_size = 0, the log disk space is allocated based onlog_disk_percentage. The default value is 0, indicating that the space is automatically calculated based on whether the log disk shares the same disk with the data disk. In scenarios where both configuration items are specified,log_disk_sizehas higher priority.
If both log_disk_size and log_disk_percentage are set to 0 (default), the disk space calculation method is as follows:
If data and CLOG share the same disk, data occupies 60% of the disk space, and CLOG occupies 30%.
If data and CLOG are on different disks, data occupies 90% of the disk space, and CLOG occupies 90%.
During the Bootstrap process, if the following error occurs, it indicates insufficient disk space:
grep 'ret=-4290' observer.log
Solution:
Correctly specify log_disk_percentage or log_disk_size. For example, specify -o log_disk_percentage=10 during startup.