【 使用环境 】测试环境
【 OB or 其他组件 】
【 使用版本 】OceanBase 4.3.5
【问题描述】obd cluster start xxx重启后提示not enough memory，启动居然要34G，无法启动。
安装设置的是 memory_limit_pecent，为 60%，总内存41G，是不是启动时对内存判断后是否能启动有逻辑问题？
obd cluster start xxxx
Get local repositories ok
Load cluster param plugin ok
Cluster status check ok
Check before start ob-configserver ok
[ERROR] OBD-2000: (172.16.0.65) not enough memory. (Free: 11G, Buff/Cache: 14G, Need: 34G), Please reduce the `memory_limit` or `memory_limit_percentage`
You can use the `obd cluster init4env wisdomob` command to automatically configure system parameters
See https://www.oceanbase.com/product/ob-deployer/error-codes .
Trace ID: ca7d99e4-a81c-11f0-af26-ac162d70e26c
If you want to view detailed obd logs, please run: obd display-trace ca7d99e4-a81c-11f0-af26-ac162d70e26c
系统内存如下
free -h
total used free shared buff/cache available
Mem: 41Gi 16Gi 11Gi 243Mi 14Gi 24Gi
Swap: 5.9Gi 0.0Ki 5.9Gi
初始配置如下
obd cluster edit-config
oceanbase-ce:
version: 4.3.5.0
release: 100000202024123117.el8
package_hash: a81cd6413fc9c42f14fdf71c55fc319dfa6cab60
172.16.0.65:
zone: zone1
servers:
- 172.16.0.65
global:
appname: xxx
root_password: xxxx
mysql_port: 2881
rpc_port: 2882
home_path: /root/xxx/oceanbase
scenario: htap
cluster_id: 1737528783
ocp_agent_monitor_password: xxx
proxyro_password: xxx
enable_syslog_wf: false
max_syslog_file_count: 4
production_mode: false
memory_limit_pecent: 60
datafile_size: 24G
system_memory: 1G
log_disk_size: 24G
cpu_count: 22
datafile_maxsize: 1T
datafile_next: 149G
depends:
- ob-configserver