服务器升级CPU后扩容Oceanbase遇到的问题

OceanBase 技术问题
#1

服务器原来是4核16G，后来升级了CPU到8核。做如下操作：

1.通过obd cluster edit-config demo修改配置文件的cpu_count到8
2.根据提示重启集群obd cluster restart demo --wp，输出如下：
（注意其中的【Reload observer x】）
Get local repositories and plugins ok
Load cluster param plugin ok
Open ssh connection ok
Cluster status check ok
Check before restart observer ok
Connect to observer ok
Server check ok
Observer restart ok
cluster scenario: htap

Wait for observer init ok
±--------------------------------------------+
| oceanbase-ce |
±----------±--------±-----±------±-------+
| ip | version | port | zone | status |
±----------±--------±-----±------±-------+
| 127.0.0.1 | 4.3.3.0 | 2881 | zone1 | ACTIVE |
±----------±--------±-----±------±-------+
obclient -h127.0.0.1 -P2881 -uroot -p’PsmbeNyHvPHlSw0oqAZF’ -Doceanbase -A

cluster unique id: 1582aeea-2f4f-5a6f-aed0-40bbfcc79391-18f3f0eb2be-00030304

Reload observer x
Check before start obagent ok
Stop obagent ok
Check before start obagent ok
Start obagent ok
obagent program health check ok
Connect to Obagent ok
±------------------------------------------------------------------+
| obagent |
±---------------±-------------------±-------------------±-------+
| ip | mgragent_http_port | monagent_http_port | status |
±---------------±-------------------±-------------------±-------+
| 172.17.116.249 | 8089 | 8088 | active |
±---------------±-------------------±-------------------±-------+
Check before start obproxy ok
Connect to obproxy ok
Stop obproxy ok
Start obproxy ok
obproxy program health check ok
Connect to obproxy ok
±--------------------------------------------+
| obproxy-ce |
±----------±-----±----------------±-------+
| ip | port | prometheus_port | status |
±----------±-----±----------------±-------+
| 127.0.0.1 | 2883 | 2884 | active |
±----------±-----±----------------±-------+
obclient -h127.0.0.1 -P2883 -uroot@proxysys -p’HirIYABMFq’ -Doceanbase -A

Check before start prometheus ok
Stop prometheus ok
Start promethues ok
prometheus program health check ok
Connect to prometheus ok
±---------------------------------------------------------+
| prometheus |
±---------------------------±------±-----------±-------+
| url | user | password | status |
±---------------------------±------±-----------±-------+
| http://172.17.116.249:9090 | admin | 4zFnU2bZOB | active |
±---------------------------±------±-----------±-------+
Check before start grafana ok
Connect to Grafana ok
Reload Grafana ok
Stop grafana ok
Start grafana ok
grafana program health check ok
Connect to Grafana ok
±---------------------------------------------------------------------+
| grafana |
±---------------------------------------±------±-----------±-------+
| url | user | password | status |
±---------------------------------------±------±-----------±-------+
| http://172.17.116.249:3000/d/oceanbase | admin | z2fQqScmOA | active |
±---------------------------------------±------±-----------±-------+
demo restart
Trace ID: dc53f9de-b77b-11ef-8902-00163e1c4550
If you want to view detailed obd logs, please run: obd display-trace dc53f9de-b77b-11ef-8902-00163e1c4550

3.通过 obd display-trace dc53f9de-b77b-11ef-8902-00163e1c4550输出的日志如下
oceanbase日志.txt (94.7 KB)
4.查看cpu_capacity还是4没有变成8

5.随即重试了obd cluster restart demo --wp了， 结果又成功了。查看了查看cpu_capacity已经变成8

自己大概看了一下错误日志，感觉都是和我操作没关系Oceanbase内部的错误，请帮忙看看什么原因

1 个赞
#4

这一步有查询记录么 发出来看一下

1 个赞
#5

没了，我是用

select zone,svr_ip,svr_port,
cpu_capacity,cpu_assigned_max,cpu_capacity-cpu_assigned_max as cpu_free,
round(memory_limit/1024/1024/1024,2) as memory_total_gb,
round((memory_limit-mem_capacity)/1024/1024/1024,2) as system_memory_gb,
round(mem_assigned/1024/1024/1024,2) as mem_assigned_gb,
round((mem_capacity-mem_assigned)/1024/1024/1024,2) as memory_free_gb,
round(log_disk_capacity/1024/1024/1024,2) as log_disk_capacity_gb,
round(log_disk_assigned/1024/1024/1024,2) as log_disk_assigned_gb,
round((log_disk_capacity-log_disk_assigned)/1024/1024/1024,2) as log_disk_free_gb,
round((data_disk_capacity/1024/1024/1024),2) as data_disk_gb,
round((data_disk_in_use/1024/1024/1024),2) as data_disk_used_gb,
round((data_disk_capacity-data_disk_in_use)/1024/1024/1024,2) as data_disk_free_gb
from gv$ob_servers;

这个SQL查询到

1 个赞
#6

这边下午在忙别的 有时间我复现一下看看

1 个赞
#7

这边并未复现成功，仅使用obd重启后就生效了。
版本为4.2.1.9。obd为2.10

1 个赞
#8

直接用用户root@sys 登录到 sys 租户，跑下面 SQL：

alter system set cpu_count=16;

测试环境，这个值可以是 8 也可以是 16. 其实不重要。总之不要是 4 ，太小了。搞得你 CPU 扩容了后 数据库还要改一道。
改了后，重启一下 OB 集群。

1 个赞