obdiag display scene信息显示不全

吉利蛋 · 2026 年4 月 22 日 19:37

【使用环境】测试环境
【 OB or 其他组件】obdiag
【使用版本】4.2.0
【问题描述】明明archive租户是3副本，为什么obdiag只显示出来2个zone，少了个zone3，看了下sys和obkv都显示正常

[admin@OB-21-64 ~]$ obdiag display scene run --scene=observer.tenant_info --env tenant_name=sys
obdiag version: 4.2.0
display_scenes_run start …
[WARN] db connection information not provided or invalid, using sys_connector
execute tasks: observer.tenant_info
±------------±------------±------------------±--------------------------------------------±------------+
| tenant_name | tenant_type | primary_zone | locality | tenant_role |
±------------±------------±------------------±--------------------------------------------±------------+
| sys | SYS | zone1,zone2;zone3 | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | PRIMARY |
±------------±------------±------------------±--------------------------------------------±------------+
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
| tenant_name | zone | observer | replica_type | cpu | memory_size | log_disk_size | data_size | required_size | unit_num |
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
| sys | zone1 | 10.0.22.44 | FULL | 3.0 | 3G | 3G | 0.39G | 0.39G | 1 |
| sys | zone2 | 10.0.22.45 | FULL | 3.0 | 3G | 3G | 0.39G | 0.39G | 1 |
| sys | zone3 | 10.0.22.46 | FULL | 3.0 | 3G | 3G | 0.39G | 0.39G | 1 |
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
Trace ID: 006a7faa-3e3f-11f1-9b7f-005056a023f8
If you want to view detailed obdiag logs, please run: obdiag display-trace 006a7faa-3e3f-11f1-9b7f-005056a023f8

obdiag latest version is 4.3.0, current version is 4.2.0, please update obdiag to the latest version
[admin@OB-21-64 ~]$ obdiag display scene run --scene=observer.tenant_info --env tenant_name=archive
obdiag version: 4.2.0
display_scenes_run start …
[WARN] db connection information not provided or invalid, using sys_connector
execute tasks: observer.tenant_info
±------------±------------±------------------±--------------------------------------------±------------+
| tenant_name | tenant_type | primary_zone | locality | tenant_role |
±------------±------------±------------------±--------------------------------------------±------------+
| archive | USER | zone1,zone2,zone3 | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 | PRIMARY |
±------------±------------±------------------±--------------------------------------------±------------+
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
| tenant_name | zone | observer | replica_type | cpu | memory_size | log_disk_size | data_size | required_size | unit_num |
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
| archive | zone1 | 10.0.22.44 | FULL | 3.0 | 4G | 12G | 0.38G | 0.38G | 1 |
| archive | zone2 | 10.0.22.45 | FULL | 3.0 | 4G | 12G | 0.38G | 0.38G | 1 |
±------------±------±-----------±-------------±----±------------±--------------±----------±--------------±---------+
Trace ID: 03bfbf8a-3e3f-11f1-924f-005056a023f8
If you want to view detailed obdiag logs, please run: obdiag display-trace 03bfbf8a-3e3f-11f1-924f-005056a023f8

obdiag latest version is 4.3.0, current version is 4.2.0, please update obdiag to the latest version

吉利蛋 · 2026 年4 月 22 日 19:45

看了几个别的也没问题呢，应该只是obdiag的展示问题，怎么修复？
mysql> SELECT SVR_IP, SVR_PORT, ZONE, STATUS, START_SERVICE_TIME
→ FROM oceanbase.DBA_OB_SERVERS;
±-----------±---------±------±-------±---------------------------+
| SVR_IP | SVR_PORT | ZONE | STATUS | START_SERVICE_TIME |
±-----------±---------±------±-------±---------------------------+
| 10.0.22.44 | 2882 | zone1 | ACTIVE | 2026-04-14 13:47:29.096512 |
| 10.0.22.45 | 2882 | zone2 | ACTIVE | 2026-04-14 13:47:33.991106 |
| 10.0.22.46 | 2882 | zone3 | ACTIVE | 2026-04-14 13:47:34.526538 |
±-----------±---------±------±-------±---------------------------+
mysql> SELECT TENANT_ID, ZONE, SVR_IP, UNIT_ID, MAX_CPU, MEMORY_SIZE FROM oceanbase.DBA_OB_UNITS where tenant_id = 1002;
±----------±------±-----------±--------±--------±------------+
| TENANT_ID | ZONE | SVR_IP | UNIT_ID | MAX_CPU | MEMORY_SIZE |
±----------±------±-----------±--------±--------±------------+
| 1002 | zone3 | 10.0.22.46 | 1001 | 3 | 4294967296 |
| 1002 | zone1 | 10.0.22.44 | 1002 | 3 | 4294967296 |
| 1002 | zone2 | 10.0.22.45 | 1003 | 3 | 4294967296 |
±----------±------±-----------±--------±--------±------------+
mysql> SELECT SVR_IP, ZONE, TENANT_ID FROM oceanbase.GV$OB_UNITS WHERE TENANT_ID = 1002;
±-----------±------±----------+
| SVR_IP | ZONE | TENANT_ID |
±-----------±------±----------+
| 10.0.22.44 | zone1 | 1002 |
| 10.0.22.46 | zone3 | 1002 |
| 10.0.22.45 | zone2 | 1002 |
±-----------±------±----------+

zone信息

obdiag latest version is 4.3.0, current version is 4.2.0, please update obdiag to the latest version

unit信息

[admin@OB-21-64 ~]$ obdiag display scene run --scene=observer.unit_info
obdiag version: 4.2.0
display_scenes_run start …
execute tasks: observer.unit_info
±---------------±----------------------------±--------±--------±-------------------±-------------------±-----------------±--------------------±--------------------±------------+
| unit_config_id | name | max_cpu | min_cpu | max_memory_size_gb | min_memory_size_gb | log_disk_size_gb | max_iops | min_iops | iops_weight |
±---------------±----------------------------±--------±--------±-------------------±-------------------±-----------------±--------------------±--------------------±------------+
| 1 | sys_unit_config | 3.0 | 3.0 | 3 | 3 | 3 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1022 | config_archive_zone2_S7_zuj | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1023 | config_archive_zone1_S7_rbl | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1024 | config_archive_zone3_S7_nfo | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1025 | config_obkv_zone1_S7_oqy | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1026 | config_obkv_zone3_S7_vgw | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
| 1027 | config_obkv_zone2_S7_kep | 3.0 | 3.0 | 4 | 4 | 12 | 9223372036854775807 | 9223372036854775807 | 3 |
±---------------±----------------------------±--------±--------±-------------------±-------------------±-----------------±--------------------±--------------------±------------+
±----------±-----------±---------±--------±-------±---------------------------±---------------------------±------±---------------±--------±--------±---------------±-----------------±--------------------±--------------------+
| tenant_id | svr_ip | svr_port | unit_id | status | create_time | modify_time | zone | unit_config_id | max_cpu | min_cpu | memory_size_gb | log_disk_size_gb | max_iops | min_iops |
±----------±-----------±---------±--------±-------±---------------------------±---------------------------±------±---------------±--------±--------±---------------±-----------------±--------------------±--------------------+
| 1 | 10.0.22.44 | 2882 | 1 | ACTIVE | 2026-02-04 16:09:45.673336 | 2026-02-04 16:09:45.673336 | zone1 | 1 | 3.0 | 3.0 | 3 | 3 | 9223372036854775807 | 9223372036854775807 |
| 1 | 10.0.22.45 | 2882 | 2 | ACTIVE | 2026-02-04 16:09:45.679603 | 2026-02-04 16:09:45.679603 | zone2 | 1 | 3.0 | 3.0 | 3 | 3 | 9223372036854775807 | 9223372036854775807 |
| 1 | 10.0.22.46 | 2882 | 3 | ACTIVE | 2026-02-04 16:09:45.682795 | 2026-02-04 16:09:45.682795 | zone3 | 1 | 3.0 | 3.0 | 3 | 3 | 9223372036854775807 | 9223372036854775807 |
| 1002 | 10.0.22.44 | 2882 | 1002 | ACTIVE | 2026-02-04 16:18:01.018106 | 2026-02-04 16:18:01.781159 | zone1 | 1023 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
| 1002 | 10.0.22.45 | 2882 | 1003 | ACTIVE | 2026-02-04 16:18:01.135681 | 2026-02-04 16:18:01.783288 | zone2 | 1022 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
| 1002 | 10.0.22.46 | 2882 | 1001 | ACTIVE | 2026-02-04 16:18:00.985464 | 2026-02-04 16:18:01.784358 | zone3 | 1024 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
| 1008 | 10.0.22.44 | 2882 | 1010 | ACTIVE | 2026-04-09 16:08:53.904587 | 2026-04-09 16:08:55.587995 | zone1 | 1025 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
| 1008 | 10.0.22.45 | 2882 | 1012 | ACTIVE | 2026-04-09 16:08:54.118637 | 2026-04-09 16:08:55.590116 | zone2 | 1027 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
| 1008 | 10.0.22.46 | 2882 | 1011 | ACTIVE | 2026-04-09 16:08:53.924748 | 2026-04-09 16:08:55.590116 | zone3 | 1026 | 3.0 | 3.0 | 4 | 12 | 9223372036854775807 | 9223372036854775807 |
±----------±-----------±---------±--------±-------±---------------------------±---------------------------±------±---------------±--------±--------±---------------±-----------------±--------------------±--------------------+

吉利蛋 · 2026 年4 月 22 日 19:52

有一个比较奇怪的点是zone3没有leader，明明primary_zone配置的是平级
mysql> select ZONE,SVR_IP,count() from DBA_OB_TABLE_LOCATIONS group by zone,svr_ip;
±------±-----------±---------+
| ZONE | SVR_IP | count() |
±------±-----------±---------+
| zone2 | 10.0.22.45 | 3968 |
| zone1 | 10.0.22.44 | 3968 |
±------±-----------±---------+
2 rows in set (0.30 sec)

AntTech_X2LONT · 2026 年4 月 22 日 21:29

学习学习

AntTech_CRNP6I · 2026 年4 月 22 日 22:01

良心发现了

AntTech_CRNP6I · 2026 年4 月 22 日 22:02

学费险恶用心

AntTech_CRNP6I · 2026 年4 月 22 日 22:02

平台期待着呢

Area · 2026 年4 月 23 日 08:46

学习一下

辞霜 · 2026 年4 月 23 日 11:31

另外俩租户正常，可能是这个租户目前有点其他问题了。obdiag是查询的系统表。
select * from cdb_ob_ls;查一下日志流看看正常么

吉利蛋 · 2026 年4 月 23 日 16:29

已经另外发了官方悬赏贴解决了，是日志流的问题~多谢

AntTech_CRNP6I · 2026 年4 月 25 日 00:10

吉他社会主义

AntTech_CRNP6I · 2026 年4 月 25 日 00:10

另外的世界

AntTech_CRNP6I · 2026 年4 月 25 日 00:10

帖准备着点

Area · 2026 年4 月 25 日 08:44

签到…