Technology sharing | observer resource water level introduction

Author: Guo Binbin

A member of the Acson DBA team, responsible for the daily problem handling of the project and the troubleshooting of the company's platform.

Source of this article: original contribution

*Produced by the Aikesheng open source community, the original content is not allowed to be used without authorization, please contact the editor and indicate the source for reprinting.


The OceanBase cluster interface will display the resource water level of the Observer. Today, let’s briefly understand the meaning of the numerical value of the resource water level and the associated parameters.

The existing test_1 cluster has only one sys tenant

Resource configuration of Sys tenant: Cpu: 2.5-5 Memory: 3G-3G Unit: 1

Cluster resource water level information

Taking 10.186.63.198 as an example, let’s take a brief look at the meanings of cpu, memory, disk and related parameters

CPU: 2.5/17 nuclei

2.5 represents the number of cpu cores allocated to the tenant on the observer, and this value is the Min CPU of the tenant

17 represents the number of CPUs available to the current observer. Usually, the observer will reserve a part of the CPU for the operating system, which is controlled by the parameter cpu_reserved

verify:

The min cpu of the current sys tenant is 2.5, and the current cluster has only one sys tenant, so the resource water level cpu shows 2.5

10.186.63.198 server cpu 19 cores

The cpu_reserved of the cluster

Therefore, except for the CPU used by the operating system, the CPU of the current observer can use up to 17 cores

Memory: 6.0/15.0GB

6.0GB represents the memory allocated by the observer. This part of memory is tenant memory + system internal memory (shared memory by all tenants). The system internal memory is controlled by system_memory, and tenant memory is controlled by resource units. 15GB represents the total amount of memory available to the current
observer , usually a part of memory is reserved for the operating system, controlled by memory_limit / memory_limit_percentage.

verify:

System internal memory size

tenant memory

System internal memory + tenant memory = 6G

Memory_limit is configured as 15G, and the total available memory of the observer is 15G

Storage: 330.0MB/47.8GB

330M represents the disk space used by the current observer

47.8G represents the total size of the current observer disk space

verify:

Log in to the sys tenant to check the storage usage of observer 10.186.63.198, the current storage usage is 330M

Log in to the server to check the disk space, and you can see that the total size of the data files after OceanBase initialization is 48G

The total available disk size displayed by the resource water level comes from SQL statistics, not obtained through system commands

Guess you like

Origin blog.csdn.net/ActionTech/article/details/130088801