fix(bugs): fixed a lot of bugs

[cndoit18]

Signed-off-by: cndoit18 cndoit18@outlook.com

Too much, I need to find Issues for it.
Can I help me together? please

fixes #643
fixes #363
fixes #692
fixes #638
fixes #613
fixes #196

---

• I've made sure the Changelog.md will remain up-to-date after this PR is merged.

[AMecea]

Hi @cndoit18, Thank you very much for your contribution! It looks good. I have only one question and a suggestion.

Sorry for the delay, I was caught in other projects. 😞

[cndoit18]

Hi @cndoit18, Thank you very much for your contribution! It looks good. I have only one question and a suggestion.

Sorry for the delay, I was caught in other projects. 😞

Thank you very much, I hope to bring more contributions to this project and be able to speed up the progress of the roadmap. I would like to ask what are the requirements to be the core maintainer of this project?

[AMecea]

Beside some minor comments all looks good. After you update the code I will merge this. Thanks again!

I would like to ask what are the requirements to be the core maintainer of this project?

We don't have yet requirements for maintainers. Please continue the good work, we would love to have more people working along us on this project. 😄

[cndoit18]

Beside some minor comments all looks good. After you update the code I will merge this. Thanks again!

I would like to ask what are the requirements to be the core maintainer of this project?

We don't have yet requirements for maintainers. Please continue the good work, we would love to have more people working along us on this project. 😄

Thank you very much for your review, it is done

[lizhongxuan]

Thanks!!!!

[cndoit18]

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

[lizhongxuan]

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

update mysqlcluster fail

2021-06-09T08:46:31.261593Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-11) starting as process 1
2021-06-09T08:46:31.273844Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-06-09T08:46:31.769019Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-06-09T08:46:32.079049Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060
2021-06-09T08:46:32.200204Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-06-09T08:46:32.263329Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=testww-mysql-0-relay-bin' to avoid this problem.
2021-06-09T08:46:32.266324Z 0 [Warning] [MY-010533] [Repl] Error during --relay-log-recovery: Could not locate rotate event from the master.
2021-06-09T08:46:32.266607Z 0 [Warning] [MY-013504] [Repl] Server was not able to find a rotate event from master server to initialize relay log recovery for channel ''. Skipping relay log recovery for the channel.
2021-06-09T08:46:32.302295Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20-11'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 11, Revision 5b5a5d2.
2021-06-09T08:46:54.305007Z 30 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2021-06-09T08:46:54.311761Z 32 [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.
2021-06-09T08:46:54.315089Z 32 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'sys_replication@testww-mysql-1.mysql.kme-mysql-10272:3306',replication started in log 'FIRST' at position 4
2021-06-09T08:46:54.319253Z 32 [ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been (server_errno=1236)
2021-06-09T08:46:54.319292Z 32 [ERROR] [MY-013114] [Repl] Slave I/O for channel '': Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been', Error_code: MY-013114

[lizhongxuan]

When update MySQL, I want to set master to read-only. How about this?

[cndoit18]

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

update mysqlcluster fail

2021-06-09T08:46:31.261593Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-11) starting as process 1
2021-06-09T08:46:31.273844Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-06-09T08:46:31.769019Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-06-09T08:46:32.079049Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060
2021-06-09T08:46:32.200204Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-06-09T08:46:32.263329Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=testww-mysql-0-relay-bin' to avoid this problem.
2021-06-09T08:46:32.266324Z 0 [Warning] [MY-010533] [Repl] Error during --relay-log-recovery: Could not locate rotate event from the master.
2021-06-09T08:46:32.266607Z 0 [Warning] [MY-013504] [Repl] Server was not able to find a rotate event from master server to initialize relay log recovery for channel ''. Skipping relay log recovery for the channel.
2021-06-09T08:46:32.302295Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20-11'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 11, Revision 5b5a5d2.
2021-06-09T08:46:54.305007Z 30 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2021-06-09T08:46:54.311761Z 32 [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.
2021-06-09T08:46:54.315089Z 32 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'sys_replication@testww-mysql-1.mysql.kme-mysql-10272:3306',replication started in log 'FIRST' at position 4
2021-06-09T08:46:54.319253Z 32 [ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been (server_errno=1236)
2021-06-09T08:46:54.319292Z 32 [ERROR] [MY-013114] [Repl] Slave I/O for channel '': Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been', Error_code: MY-013114

Did you create a new mysqlcluster? If it's old, you should have problems with dirty data, do you have slack? We can use it to chat

[lizhongxuan]

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

update mysqlcluster fail

2021-06-09T08:46:31.261593Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-11) starting as process 1
2021-06-09T08:46:31.273844Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-06-09T08:46:31.769019Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-06-09T08:46:32.079049Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060
2021-06-09T08:46:32.200204Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-06-09T08:46:32.263329Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=testww-mysql-0-relay-bin' to avoid this problem.
2021-06-09T08:46:32.266324Z 0 [Warning] [MY-010533] [Repl] Error during --relay-log-recovery: Could not locate rotate event from the master.
2021-06-09T08:46:32.266607Z 0 [Warning] [MY-013504] [Repl] Server was not able to find a rotate event from master server to initialize relay log recovery for channel ''. Skipping relay log recovery for the channel.
2021-06-09T08:46:32.302295Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20-11'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 11, Revision 5b5a5d2.
2021-06-09T08:46:54.305007Z 30 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2021-06-09T08:46:54.311761Z 32 [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.
2021-06-09T08:46:54.315089Z 32 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'sys_replication@testww-mysql-1.mysql.kme-mysql-10272:3306',replication started in log 'FIRST' at position 4
2021-06-09T08:46:54.319253Z 32 [ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been (server_errno=1236)
2021-06-09T08:46:54.319292Z 32 [ERROR] [MY-013114] [Repl] Slave I/O for channel '': Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been', Error_code: MY-013114

Did you create a new mysqlcluster? If it's old, you should have problems with dirty data, do you have slack? We can use it to chat

new mysqlcluster. wechart ?

[cndoit18]

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

update mysqlcluster fail

2021-06-09T08:46:31.261593Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-11) starting as process 1
2021-06-09T08:46:31.273844Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-06-09T08:46:31.769019Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-06-09T08:46:32.079049Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060
2021-06-09T08:46:32.200204Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-06-09T08:46:32.263329Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=testww-mysql-0-relay-bin' to avoid this problem.
2021-06-09T08:46:32.266324Z 0 [Warning] [MY-010533] [Repl] Error during --relay-log-recovery: Could not locate rotate event from the master.
2021-06-09T08:46:32.266607Z 0 [Warning] [MY-013504] [Repl] Server was not able to find a rotate event from master server to initialize relay log recovery for channel ''. Skipping relay log recovery for the channel.
2021-06-09T08:46:32.302295Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20-11'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 11, Revision 5b5a5d2.
2021-06-09T08:46:54.305007Z 30 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2021-06-09T08:46:54.311761Z 32 [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.
2021-06-09T08:46:54.315089Z 32 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'sys_replication@testww-mysql-1.mysql.kme-mysql-10272:3306',replication started in log 'FIRST' at position 4
2021-06-09T08:46:54.319253Z 32 [ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been (server_errno=1236)
2021-06-09T08:46:54.319292Z 32 [ERROR] [MY-013114] [Repl] Slave I/O for channel '': Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been', Error_code: MY-013114

Did you create a new mysqlcluster? If it's old, you should have problems with dirty data, do you have slack? We can use it to chat

new mysqlcluster. wechart ?

Thanks!!!!

It is recommended that you turn on graceful scheduling for more stability

update mysqlcluster fail

2021-06-09T08:46:31.261593Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-11) starting as process 1
2021-06-09T08:46:31.273844Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-06-09T08:46:31.769019Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-06-09T08:46:32.079049Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060
2021-06-09T08:46:32.200204Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-06-09T08:46:32.263329Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=testww-mysql-0-relay-bin' to avoid this problem.
2021-06-09T08:46:32.266324Z 0 [Warning] [MY-010533] [Repl] Error during --relay-log-recovery: Could not locate rotate event from the master.
2021-06-09T08:46:32.266607Z 0 [Warning] [MY-013504] [Repl] Server was not able to find a rotate event from master server to initialize relay log recovery for channel ''. Skipping relay log recovery for the channel.
2021-06-09T08:46:32.302295Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20-11'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 11, Revision 5b5a5d2.
2021-06-09T08:46:54.305007Z 30 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL '' executed'. Previous state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='testww-mysql-1.mysql.kme-mysql-10272', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
2021-06-09T08:46:54.311761Z 32 [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.
2021-06-09T08:46:54.315089Z 32 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'sys_replication@testww-mysql-1.mysql.kme-mysql-10272:3306',replication started in log 'FIRST' at position 4
2021-06-09T08:46:54.319253Z 32 [ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been (server_errno=1236)
2021-06-09T08:46:54.319292Z 32 [ERROR] [MY-013114] [Repl] Slave I/O for channel '': Got fatal error 1236 from master when reading data from binary log: 'Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been', Error_code: MY-013114

Did you create a new mysqlcluster? If it's old, you should have problems with dirty data, do you have slack? We can use it to chat

new mysqlcluster. wechart ?

Ok, what is yours?

[lizhongxuan]

Thanks @cndoit18 , I forgot to update the image of mysql-operator-sidecar , MySQLCluster is working properly.