Oceanbase 从4.3.4.0升级到4.3.5.0失败

OceanBase 技术问题
, ,
#1 
Connect to observer 172.16.0.65:2881 ok
+-------------------------------------------------------------------------------------------------------------+
|                                            Packages Will Be Used                                            |
+--------------+---------+------------------------+--------+------------------------------------------+-------+
| name         | version | release                | arch   | md5                                      | mark  |
+--------------+---------+------------------------+--------+------------------------------------------+-------+
| oceanbase-ce | 4.3.4.0 | 100000162024110717.el7 | x86_64 | 5d59e837a0ecff1a6baa20f72747c343ac7c8dce | start |
| oceanbase-ce | 4.3.5.0 | 100000202024123117.el7 | x86_64 | 48b61655aaa13e9b01b722928d1979c76b41937e | dest  |
+--------------+---------+------------------------+--------+------------------------------------------+-------+
If you use a non-official release, we cannot guarantee a successful upgrade or technical support when you fail. Make sure that you want to use the above package to upgrade. [y/n]: If you use a non-official release, we cannot guarantee a successful upgrade or technical support when you fail. Make sure that you want to use the above package to upgrade. [y/n]: y
cluster scenario: htap
Start observer ok
observer program health check ok
obshell program health check ok
observer program health check ok
Connect to observer 172.16.0.65:2881 ok
Exec upgrade_checker.py ok
Exec upgrade_pre.py ok
Exec upgrade_health_checker.py ok
Upgrade ok
cluster scenario: htap

Exec upgrade_post.py x
See https://www.oceanbase.com/product/ob-deployer/error-codes .
Trace ID: 154f75a0-d2e4-11ef-9f68-ac162d70e26c
If you want to view detailed obd logs, please run: obd display-trace 154f75a0-d2e4-11ef-9f68-ac162d70e26c

trace见下面附件。
集群状态一直是upgrading

[root@localhost etc]# obd cluster list
+--------------------------------------------------------------+
|                         Cluster List                         |
+------------+-------------------------------+-----------------+
| Name       | Configuration Path            | Status (Cached) |
+------------+-------------------------------+-----------------+
| wisdombase | /root/.obd/cluster/wisdombase | upgrading       |
+------------+-------------------------------+-----------------+

登录进去后，select version();发现版本却是新4.3.5.0

obclient [oceanbase]> select version();
+------------------------------+
| version()                    |
+------------------------------+
| 5.7.25-OceanBase_CE-v4.3.5.0 |
+------------------------------+

但是通过4.3.5.0新增的视图进行测试时，并没有新的视图，说明不是最新的4.3.5.0版本？

obclient [oceanbase]> SELECT * FROM SYS.DBA_OB_TABLE_SPACE_USAGE WHERE ROWNUM <= 3;
ERROR 1146 (42S02): Table 'SYS.DBA_OB_TABLE_SPACE_USAGE' doesn't exist
obclient [oceanbase]> SELECT * FROM oceanbase.DBA_OB_TABLE_SPACE_USAGE LIMIT 3;
ERROR 1146 (42S02): Table 'oceanbase.DBA_OB_TABLE_SPACE_USAGE' doesn't exist

trace.txt (100.6 KB)

#4

/tmp/172.16.0.65:2882/48b61655aaa13e9b01b722928d1979c76b41937e/upgrade_post.py"
到这个路径下找一下看看有没有upgrade_post.log日志麻烦发出来一份

#5

只有这些文件

[root@localhost 48b61655aaa13e9b01b722928d1979c76b41937e]# ls
default_parameter.json        oceanbase_upgrade_dep.yml  upgrade_post_extract_files_2025_01_15_10_04_45_053728_anDaHioJ
default_srs_data_mysql.sql    timezone_V1.log            upgrade_post.py
default_system_variable.json  upgrade_checker.py         upgrade_pre_extract_files_2025_01_15_10_01_13_367031_dki98zQN
fill_help_tables-ob.sql       upgrade_health_checker.py  upgrade_pre.py
#6

查看下你执行升级命令时候的当前目录下

#7

upgrade_post.log (8.2 KB)

#8

你好麻烦再提供一份升级期间的observer日志。

#9

早上距离现在只有下面这些了，最早一个都是14:00左右的，貌似被覆盖了？

[root@localhost log]# ls -l
总用量 1481984
drwxr-xr-x 2 root root      4096 11月 29 18:20 alert
-rw-r--r-- 1 root root  91271472 1月  15 14:56 election.log
-rw-r--r-- 1 root root     22125 1月  15 09:48 election.log.wf
-rw-r--r-- 1 root root 175148328 1月  15 14:56 observer.log
-rw-r--r-- 1 root root 268438038 1月  15 14:24 observer.log.20250115142452345
-rw-r--r-- 1 root root 268436861 1月  15 14:36 observer.log.20250115143629881
-rw-r--r-- 1 root root 268435541 1月  15 14:48 observer.log.20250115144830493
-rw-r--r-- 1 root root   1811005 1月  15 14:48 observer.log.wf
-rw-r--r-- 1 root root  42263015 1月  15 14:56 rootservice.log
-rw-r--r-- 1 root root 268435631 1月  15 14:21 rootservice.log.20250115142145811
-rw-r--r-- 1 root root     90270 1月  15 14:21 rootservice.log.wf
-rw-r--r-- 1 root root 133117645 1月  15 14:55 trace.log
#10

SELECT * FROM oceanbase.DBA_OB_CLUSTER_EVENT_HISTORY WHERE MODULE=‘UPGRADE’\G; 这个信息查询一下

#11

我再重新执行一次升级命令，obd cluster upgrade xxx -c oceanbase-ce -V 4.3.5.0 --usable=08314aa05c1993c6df2bf3bfb867ea0df85f2b234c31226524d352d99f781f50，现在却顺利升级通过了- -！那暂时不找原因了，感谢哈

#12

我再重新执行一次升级命令，obd cluster upgrade xxx -c oceanbase-ce -V 4.3.5.0 --usable=08314aa05c1993c6df2bf3bfb867ea0df85f2b234c31226524d352d99f781f50，现在却顺利升级通过了- -！那暂时不找原因了，感谢哈

1 个赞