OB磁盘分配和OCP显示问题

【 使用环境 】生产环境
【 OB or 其他组件 】OB
【 使用版本 】4.3.5.3
【问题描述】


看OCP上数据盘使用量是22935.84/26624 GiB ,但是我从参数里看配置的上限是35T,步长1T:
obclient [(none)]> show parameters where svr_ip=‘192.168.192.111’ and name like ‘datafile%’;
±------±---------±----------------±---------±-------------------------±----------±------±------------------------------------------------------------------------------±--------±--------±--------±------------------±--------------±----------+
| zone | svr_type | svr_ip | svr_port | name | data_type | value | info | section | scope | source | edit_level | default_value | isdefault |
±------±---------±----------------±---------±-------------------------±----------±------±------------------------------------------------------------------------------±--------±--------±--------±------------------±--------------±----------+
| zone3 | observer | 192.168.192.111 | 2882 | datafile_disk_percentage | INT | 0 | the percentage of disk space used by the data files. Range: [0,99] in integer | SSTABLE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0 | 1 |
| zone3 | observer | 192.168.192.111 | 2882 | datafile_maxsize | CAPACITY | 35T | the auto extend max size. Range: [0, +∞) | SSTABLE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0 | 0 |
| zone3 | observer | 192.168.192.111 | 2882 | datafile_next | CAPACITY | 1T | the auto extend step. Range: [0, +∞) | SSTABLE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0 | 0 |
| zone3 | observer | 192.168.192.111 | 2882 | datafile_size | CAPACITY | 10T | size of the data file. Range: [0, +∞) | SSTABLE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0M | 0 |
±------±---------±----------------±---------±-------------------------±----------±------±------------------------------------------------------------------------------±--------±--------±--------±------------------±--------------±----------+
4 rows in set (0.014 sec)

[root@OB192-111 data]# df -h /data/1
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_data-lv_data 42T 27T 16T 63% /data/1

df -h 看是27T/42T,请问这是现在根据步长扩容到27T了的意思吗,什么时候会触发扩容

4 个赞


关键是同集群的另一台机器是35T上限,没有红,就挺奇怪的

ocp版本多少
再查一下 log_disk%参数都是多少
log和data是同盘么

ocp是最新的4.4.2

obclient [(none)]> show parameters where svr_ip=‘192.168.192.111’ and name like ‘log_disk%%’;
±------±---------±----------------±---------±-------------------------------------±----------±------±------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------±-----------±--------±--------±------------------±--------------±----------+
| zone | svr_type | svr_ip | svr_port | name | data_type | value | info | section | scope | source | edit_level | default_value | isdefault |
±------±---------±----------------±---------±-------------------------------------±----------±------±------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------±-----------±--------±--------±------------------±--------------±----------+
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_percentage | INT | 0 | the percentage of disk space used by the log files. Range: [0,99] in integer;only effective when parameter log_disk_size is 0;when log_disk_percentage is 0: a) if the data and the log are on the same disk, means log_disk_percentage = 30 b) if the data and the log are on the different disks, means log_disk_perecentage = 90 | LOGSERVICE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0 | 1 |
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_size | CAPACITY | 3000G | the size of disk space used by the log files. Range: [0, +∞) | LOGSERVICE | CLUSTER | DEFAULT | DYNAMIC_EFFECTIVE | 0M | 0 |
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_throttling_maximum_duration | TIME | 2h | maximum duration of log disk throttling, that is the time remaining until the log disk space is exhausted after log disk throttling triggered. | LOGSERVICE | TENANT | DEFAULT | DYNAMIC_EFFECTIVE | 2h | 1 |
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_throttling_percentage | INT | 60 | the threshold of the size of the log disk when writing_limit will be triggered. Rang:[40,100]. setting 100 means turn off writing limit | LOGSERVICE | TENANT | DEFAULT | DYNAMIC_EFFECTIVE | 60 | 1 |
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_utilization_threshold | INT | 80 | log disk utilization threshold before reuse log files, should be smaller than log_disk_utilization_limit_threshold. Range: [10, 100) | LOGSERVICE | TENANT | DEFAULT | DYNAMIC_EFFECTIVE | 80 | 1 |
| zone3 | observer | 192.168.192.111 | 2882 | log_disk_utilization_limit_threshold | INT | 95 | maximum of log disk usage percentage before stop submitting or receiving logs, should be bigger than log_disk_utilization_threshold. Range: [80, 100] | LOGSERVICE | TENANT | DEFAULT | DYNAMIC_EFFECTIVE | 95 | 1 |
±------±---------±----------------±---------±-------------------------------------±----------±------±------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------±-----------±--------±--------±------------------±--------------±----------+
6 rows in set (0.012 sec)

log和data不是同盘

磁盘参数有改过么
select * from GV$OB_SERVERS;

obclient [oceanbase]> select * from GV$OB_SERVERS where svr_ip in (‘192.168.192.110’,‘192.168.192.111’);
±----------------±---------±------±---------±-------------±-----------------±-------------±-----------------±-------------±-------------±------------------±------------------±----------------±-------------------±-------------------±-----------------±------------------------±-------------±--------------------±------------------------±----------------------±---------------------------------±----------------------------+
| SVR_IP | SVR_PORT | ZONE | SQL_PORT | CPU_CAPACITY | CPU_CAPACITY_MAX | CPU_ASSIGNED | CPU_ASSIGNED_MAX | MEM_CAPACITY | MEM_ASSIGNED | LOG_DISK_CAPACITY | LOG_DISK_ASSIGNED | LOG_DISK_IN_USE | DATA_DISK_CAPACITY | DATA_DISK_ASSIGNED | DATA_DISK_IN_USE | DATA_DISK_HEALTH_STATUS | MEMORY_LIMIT | DATA_DISK_ALLOCATED | DATA_DISK_ABNORMAL_TIME | SSL_CERT_EXPIRED_TIME | SS_DATA_DISK_OPERATION_SUGGESTED | SS_DATA_DISK_SIZE_SUGGESTED |
±----------------±---------±------±---------±-------------±-----------------±-------------±-----------------±-------------±-------------±------------------±------------------±----------------±-------------------±-------------------±-----------------±------------------------±-------------±--------------------±------------------------±----------------------±---------------------------------±----------------------------+
| 192.168.192.111 | 2882 | zone3 | 2881 | 128 | 128 | 28 | 28 | 397413496652 | 77309411328 | 3221225472000 | 395136991232 | 288769441792 | 38482906972160 | NULL | 24626939822080 | NORMAL | 431971192012 | 28587302322176 | NULL | NULL | NULL | NULL |
| 192.168.192.110 | 2882 | zone3 | 2881 | 128 | 128 | 21.5 | 21.5 | 397413502681 | 66571993088 | 3221225472000 | 362924736512 | 290715598848 | 38482906972160 | NULL | 24642869788672 | NORMAL | 431971198566 | 38482906972160 | NULL | NULL | NULL | NULL |
±----------------±---------±------±---------±-------------±-----------------±-------------±-----------------±-------------±-------------±------------------±------------------±----------------±-------------------±-------------------±-----------------±------------------------±-------------±--------------------±------------------------±----------------------±---------------------------------±----------------------------+
2 rows in set (0.006 sec)

ocp查询的是这个GV$OB_SERVERS;
DATA_DISK_ALLOCATED 已分配的数据盘大小两节点不一致导致。
什么原因还需要再分析下,这套集群是如何部署的

应该是OCP部署的,怎么产生的先放一边吧,能否先帮忙解决这个问题。
DATA_DISK_ALLOCATED能通过什么方式触发一下调整吗,最好就是到35T和192.110对齐

修改datafile_size为35T即可
但是你集群给的10T目前自增到35或28也是不符合预期的

好的,我调整下。
自增这个问题目前不影响使用就行,暂时不研究了,把这个异常的红色条子去掉就行 :face_exhaling:

使用的集群是否做过什么修改磁盘参数操作呢?

估计是什么历史原因,问不到了,我只能基于现状处理了