MGR 滚动升级数据库版本报错
环境：产线old：8.0.32-25
new：8.0.32-26
升级方式： inplace 直接替换包然后启动
加入节点报错如下:
2024-08-06T22:36:22.184209+08:00 141 Plugin group_replication reported: 'Establishing connection to a group replication recovery donor 02bc892f-232a-11ef-a687-2800aff523fc at 172.16.179.22 port: 3306.'
2024-08-06T22:36:22.184579+08:00 142 Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2024-08-06T22:36:22.185049+08:00 142 Slave I/O thread for channel 'group_replication_recovery': connected to master 'repl@172.16.179.22:3306',replication started in log 'FIRST' at position 4
2024-08-06T22:36:22.228851+08:00 0 Plugin group_replication reported: ' read_msg sets CON_PROTO for fd:329 in mark, tag:313'
2024-08-06T22:36:22.228873+08:00 0 Plugin group_replication reported: ' read_msg sets CON_PROTO for fd:330 in mark, tag:313'
2024-08-06T22:36:22.228886+08:00 0 Plugin group_replication reported: ' proto is done for fd:329'
2024-08-06T22:36:22.228914+08:00 0 Plugin group_replication reported: ' proto is done for fd:330'
2024-08-06T22:36:22.240455+08:00 143 Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './m-node1-relay-bin-group_replication_recovery.000001' position: 4
2024-08-06T14:36:23Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID=531c3f9a0bd2b9927ad15adeeb1c651bf5df0d72
Build ID: Not Available
Server Version: 8.0.32-26 GreatSQL, Release 26, Revision a68b3034c3d
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x80000
/usr/local/GreatSQL/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d)
/usr/local/GreatSQL/bin/mysqld(print_fatal_signal(int)+0x3cf)
/usr/local/GreatSQL/bin/mysqld(handle_fatal_signal+0xc5)
/usr/lib64/libpthread.so.0(+0xf630)
/usr/lib64/libc.so.6(+0x1566a6)
/usr/local/GreatSQL/lib/plugin/greatdb_ha.so(+0x11605)
/usr/local/GreatSQL/lib/plugin/greatdb_ha.so(+0x1d9c7)
/usr/lib64/libpthread.so.0(+0x7ea5)
/usr/lib64/libc.so.6(clone+0x6d)
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2024-08-06T22:36:25.631470+08:00 0 The syntax 'log_slow_slave_statements' is deprecated and will be removed in a future release. Please use log_slow_replica_statements instead.
2024-08-06T22:36:25.631515+08:00 0 The syntax 'slave_parallel_type' is deprecated and will be removed in a future release. Please use replica_parallel_type instead.
2024-08-06T22:36:25.631523+08:00 0 The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2024-08-06T22:36:25.631533+08:00 0 The syntax 'slave_parallel_workers' is deprecated and will be removed in a future release. Please use replica_parallel_workers instead.
2024-08-06T22:36:25.631543+08:00 0 The syntax 'slave_preserve_commit_order' is deprecated and will be removed in a future release. Please use replica_preserve_commit_order instead.
2024-08-06T22:36:25.631553+08:00 0 The syntax 'slave_checkpoint_period' is deprecated and will be removed in a future release. Please use replica_checkpoint_period instead.
2024-08-06T22:36:25.631743+08:00 0 Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2024-08-06T22:36:25.631754+08:00 0 Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2024-08-06T22:36:25.631821+08:00 0 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
8.0.26开始新增选项 group_replication_view_change_uuid，因此不支持在一个MGR集群中，同时包含8.0.26以前及以后的版本
详见：https://greatsql.cn/docs/8.0.32-26/7-migrate-and-upgrade/1-upgrade-to-greatsql8.html KAiTO 发表于 2024-8-7 10:30
8.0.26开始新增选项 group_replication_view_change_uuid，因此不支持在一个MGR集群中，同时包含8.0.26以前 ...
那如果我停机，把三个节点 分别升级 然后再重建mgr可以吗？ 两个问题：
1. 8.0.26开始新增选项 group_replication_view_change_uuid，因此不支持在一个MGR集群中，同时包含8.0.26以前及以后的版本。
2. MySQL 8.0.26不支持greatdb_ha plugin，也要先去掉。
综上，如果有个MGR集群需要跨8.0.25版本的升级，则需要整个集群停机，逐个节点升级，最后再重新拉起MGR。或者构建两个不同版本的MGR集群，它们之间用主从复制连接，再完成切换升级。
更多关于8.0.25升级到8.0.32的方法可参考：https://greatsql.cn/thread-825-1-2.html mabai 发表于 2024-8-7 10:41
那如果我停机，把三个节点 分别升级 然后再重建mgr可以吗？
是的，3个节点都停机，都完成升级后再次拉起MGR就可以。
页:
[1]