MySQL 8.0.22 已发布，更新了很多问题，但同时存在严重问题，请大家慎升级

最近看到8.0.22发布，这迫不及待的升了级，结果造成了整个系统瘫痪。

我决定使用8.0版本是从8.0.18开始的

最开始的时候8.0.18还是8.0.19发布有个BUG，但在新版本版中很快就修复了，很惊喜，但这些bug不是引起不能用，而是个别功能使用上的问题。

所以就从8.0.18-->8.0.19--8.0.20--8.0.21这样的版本升上来，之所以直接升，由于害怕如果版本跨度太大就会造成升级问题更多，所以就这样一路升下来。

现在8.0.21使用的过程中也有些问题，但还是可以使用的，8.0.21经常出现的问题。

2020-10-20T01:16:28.587229+08:00 0 [Warning] [MY-011493] [Repl] Plugin group_replication reported: 'Member with address MySQLCluster3:3306 has become unreachable.'
2020-10-20T01:16:28.850342+08:00 0 [Warning] [MY-011493] [Repl] Plugin group_replication reported: 'Member with address MySQLCluster4:3306 has become unreachable.'
2020-10-20T01:16:29.172527+08:00 0 [ERROR] [MY-011495] [Repl] Plugin group_replication reported: 'This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.'
2020-10-20T01:16:30.002691+08:00 0 [Warning] [MY-011494] [Repl] Plugin group_replication reported: 'Member with address MySQLCluster3:3306 is reachable again.'
2020-10-20T01:16:30.162834+08:00 0 [Warning] [MY-011494] [Repl] Plugin group_replication reported: 'Member with address MySQLCluster4:3306 is reachable again.'
2020-10-20T01:16:30.162875+08:00 0 [Warning] [MY-011498] [Repl] Plugin group_replication reported: 'The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.'
2020-10-20T01:16:32.585380+08:00 0 [ERROR] [MY-011505] [Repl] Plugin group_replication reported: 'Member was expelled from the group due to network failures, changing member status to ERROR.'
2020-10-20T01:16:33.085355+08:00 339730 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.105305+08:00 339730 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.278873+08:00 0 [Warning] [MY-011630] [Repl] Plugin group_replication reported: 'Due to a plugin error, some transactions were unable to be certified and will now rollback.'
2020-10-20T01:16:33.279107+08:00 362245 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 362245'
2020-10-20T01:16:33.279176+08:00 331023 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 331023'
2020-10-20T01:16:33.279238+08:00 362245 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279258+08:00 363044 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 363044'
2020-10-20T01:16:33.279282+08:00 363039 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 363039'
2020-10-20T01:16:33.279411+08:00 362247 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 362247'
2020-10-20T01:16:33.279213+08:00 362405 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 362405'
2020-10-20T01:16:33.279288+08:00 331023 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279362+08:00 363044 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279427+08:00 363055 [ERROR] [MY-011615] [Repl] Plugin group_replication reported: 'Error while waiting for conflict detection procedure to finish on session 363055'
2020-10-20T01:16:33.279655+08:00 363055 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279240+08:00 0 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2020-10-20T01:16:33.279417+08:00 363039 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279521+08:00 362405 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.279524+08:00 362247 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.359462+08:00 363007 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.359611+08:00 363007 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.419561+08:00 362247 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.419667+08:00 362247 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.440388+08:00 362247 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.440465+08:00 362247 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.476476+08:00 363007 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.476569+08:00 363007 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.737831+08:00 362987 [ERROR] [MY-011601] [Repl] Plugin group_replication reported: 'Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin'
2020-10-20T01:16:33.737938+08:00 362987 [ERROR] [MY-010207] [Repl] Run function 'before_commit' in plugin 'group_replication' failed
2020-10-20T01:16:33.940287+08:00 363057 [System] [MY-011565] [Repl] Plugin group_replication reported: 'Setting super_read_only=ON.'
2020-10-20T01:16:33.941250+08:00 363058 [Warning] [MY-013373] [Repl] Plugin group_replication reported: 'Started auto-rejoin procedure attempt 1 of 10'
2020-10-20T01:16:34.206314+08:00 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.'
2020-10-20T01:16:36.894778+08:00 363059 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 616884182, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2020-10-20T01:16:37.827466+08:00 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error on opening a connection to MySQLCluster1:33061 on local port: 33061.'
2020-10-20T01:16:39.687389+08:00 363058 [Warning] [MY-013375] [Repl] Plugin group_replication reported: 'Auto-rejoin procedure attempt 1 of 10 finished. Member was able to join the group.'
2020-10-20T01:16:40.688670+08:00 0 [System] [MY-013471] [Repl] Plugin group_replication reported: 'Distributed recovery will transfer data using: Incremental recovery from a group donor'
2020-10-20T01:16:40.855095+08:00 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to MySQLCluster4:3306, MySQLCluster2:3306, MySQLCluster3:3306 on view 16023787958066179:98.'
2020-10-20T01:16:41.904947+08:00 363066 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='MySQLCluster3', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2020-10-20T01:16:42.868450+08:00 363067 [Warning] [MY-010897] [Repl] 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.
2020-10-20T01:16:43.718617+08:00 363067 [System] [MY-010562] [Repl] Slave I/O thread for channel 'group_replication_recovery': connected to master 'mysql_innodb_cluster_2@MySQLCluster3:3306',replication started in log 'FIRST' at position 4
2020-10-20T01:17:09.590907+08:00 363066 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='MySQLCluster3', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2020-10-20T01:17:13.298096+08:00 0 [System] [MY-011490] [Repl] Plugin group_replication reported: 'This server was declared online within the replication group.'
2020-10-20T05:58:57.491146+08:00 364813 [Warning] [MY-010055] [Server] IP address '94.232.40.199' could not be resolved: Name or service not known
2020-10-20T21:12:34.981110+08:00 370740 [Warning] [MY-010055] [Server] IP address '94.232.40.199' could not be resolved: Name or service not known

但报这个错误的时候，可以确认的是网络没有问题，由于这几个机都在一个路由下的虚拟机中。

由于不知为什么会造成master迁移，并且最终造成整个集群停摆，所以在8.0.22发布后以为解决了这些问题，但是结果就惨了。

把集群中机都升级后，也把router升级后，开始发布新版router连接不了集群，但发现8.0.21的router是可以正常连接集群的，结果又发布mysql程序在不断重启，所以造成master不断移交，看日志报出的问题如下：
2020-10-23T08:46:20.969540+08:00 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-10-23T08:46:21.001543+08:00 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2020-10-23T08:46:21.008510+08:00 0 [System] [MY-010232] [Server] XA crash recovery finished.
2020-10-23T08:46:21.115556+08:00 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-23T08:46:21.115964+08:00 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-23T08:46:21.145324+08:00 0 [ERROR] [MY-010544] [Repl] Failed to open the relay log './MySQLCluster3-relay-bin.000001' (relay_log_pos 4).
2020-10-23T08:46:21.145714+08:00 0 [ERROR] [MY-011059] [Repl] Could not find target log file mentioned in relay log info in the index file './relay-log.index' during relay log initialization.
2020-10-23T08:46:21.146520+08:00 0 [ERROR] [MY-010426] [Repl] Slave: Failed to initialize the master info structure for channel ''; its record may still be present in 'mysql.slave_master_info' table, consider deleting it.
2020-10-23T08:46:21.146890+08:00 0 [ERROR] [MY-010529] [Repl] Failed to create or recover replication info repositories.
2020-10-23T08:46:21.170810+08:00 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.22'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server - GPL.
00:46:22 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f5f9000bef0
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 = 7f625069fca0 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x202b02e]
/usr/sbin/mysqld(handle_fatal_signal+0x323) [0x1024333]
/lib64/libpthread.so.0() [0x3eb300f7e0]
/usr/sbin/mysqld(Item_func_sp::get_initial_pseudo_tables() const+0x11) [0x11b6c71]
/usr/sbin/mysqld(Item_func::update_used_tables()+0x19) [0x11b5f79]
/usr/sbin/mysqld(Item_func_sp::update_used_tables()+0x11) [0x11b6d91]
/usr/sbin/mysqld(SELECT_LEX::update_used_tables()+0x9f) [0xf25acf]
/usr/sbin/mysqld(JOIN::destroy()+0x578) [0xf41258]
/usr/sbin/mysqld(SELECT_LEX::cleanup(THD*, bool)+0x65) [0xfb1855]
/usr/sbin/mysqld(SELECT_LEX_UNIT::cleanup(THD*, bool)+0xa6) [0xfb19d6]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0xb51) [0xeed1d1]
/usr/sbin/mysqld(mysql_parse(THD*, Parser_state*)+0x3f8) [0xef18f8]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x170b) [0xef347b]
/usr/sbin/mysqld(do_command(THD*)+0x174) [0xef49a4]
/usr/sbin/mysqld() [0x1015d10]
/usr/sbin/mysqld() [0x25581bc]
/lib64/libpthread.so.0() [0x3eb3007aa1]
/lib64/libc.so.6(clone+0x6d) [0x3eb28e8c4d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f5f9002be48): is an invalid pointer
Connection ID (thread ID): 228
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2020-10-23T08:46:23.131822+08:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22) starting as process 18720
2020-10-23T08:46:23.143107+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-23T08:46:30.031105+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.

这时候已无法退到原来的8.0.21了，欲哭无泪。

好吧，想着不行就装一台8.0.21，然后加到集群，让它自动复制一份吧，结果又告诉说是8.0.22不带8.0.21玩，也就是8.0.21中加不进8.0.21的MySQL，操蛋。

经讨论可能是8.0.21的数据文件与8.0.22的数据文件不一致，所以造成这个问题，好吧，重装8.0.22，重导（非集群内部之间的复制，使用的是mysqldump，结果是很慢，非常慢，痛苦），相关于数据重做，好吧，一个一个装好数据也弄好，集群起来了，结果发现一写数据一操作就还是原来的情况，再后来想，集群不行我就用单台吧，解散集群，只用一台服务，结果发现，问题依旧，单个mysql运行也是一样的，出现上面异常后并且会造成数据库自动变为只读状态。

最终结果把mysql 重新装回8.0.21,组建集群，使用router的8.0.21版本，总算可以了，这个过程造成我一个晚上没有合眼，非常痛苦的经历和教训。

这mysql发布都不测试的吗？？？？