Blue Green Deployment

Thanks Manish for the response, but none of that is showing. The DB was upgraded to Driver 8 but my Dashboard is not showing the above. It is the same as before I switched over. Thanks.

Hi Manish. Yes, I set the timeout as the default, (5 min) but nothing was reported back. On looking at the event log now I get the following:-

Read Replica Replication Error - SQLError: 1064, reason: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'ANONYMOUS' at source log mysql-bin-changelog.252646, end_log_pos 994. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any. - every minute.

I am scared to change anything as our clients are already processing their data to the DB.

Your advice is greatly appreciated.

Thanks Terry

Hi Terry

Does it have any Event on log & event , i assume it might have timeout and not completed the switch over , let me try in my lab too.. Switchover timeout

Switchover timeout : You can specify a switchover timeout period between 30 seconds and 3,600 seconds (one hour). If the switchover takes longer than the specified duration, then any changes are rolled back and no changes are made to either environment. The default timeout period is 300 seconds (five minutes).

Hope it helps and if it does, I would appreciate if answer can be accepted so that community can benefit for clarity when searching for similar enquiries in repost/aws guide.

Hello

Please check as following .

After a switchover, the DB instances in the previous blue environment are retained.

RDS renames the DB instances in the blue environment by appending -oldn to the current resource name, where n is a number. The DB instances are read-only until you set the read_only parameter to 0.

ref : After switchover

Hope it helps and if it does, I would appreciate if answer can be accepted so that community can benefit for clarity when searching for similar enquiries in repost/aws guide.

Hi Terry

How is the replication lag , i assume it would be high as some transaction are not executed , and replication is still running .

The MySQL 1064 error is a syntax error. This means the reason is because MySQL doesn’t understand what application/sqlcode asking it to do. However, there are many different situations that can lead to this type of miscommunication among database.

The simplest cause is that application may be attempting to use outdated or even obsolete commands that can’t be read. It may also be possible that application may have attempted to include a ‘reserved word’ in one of application commands. Reserved words are terms that can only be used in specific contexts in MySQL.

If you attempt to use them in other ways, you’ll be faced with an error. When you make a request via MySQL which references data that isn’t where it’s supposed to be, you’ll also see the 1064 error.

"Read Replica Replication Error - SQLError: 1064, reason: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'ANONYMOUS' at source log mysql-bin-changelog.252646, end_log_pos 994. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any."

This is a general error for multi-threaded binlog replication, can you please run the following commands to see the output:

-> SELECT * FROM performance_schema.replication_applier_status_by_worker;

Please also run this command and check which sql is not being executed

-> SHOW BINLOG EVENTS [IN 'mysql-bin-changelog.252646'] [FROM 994]

[+] https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-download-binary-logs/

Even if you are creating new replica or using B/G deployment to upgrade the version from 5.7 to 8.0, you would need address the core issue of MySQL 1064.

I recommend you to refer below article which provides you information on what has changed in MySQL 8.0 from 5.7.

[+] https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html [+] https://kinsta.com/knowledgebase/mysql-error-1064/

[1]Replication and Reserved Words - https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-features-reserved-words.html [2] MySQL 8.0 Keywords and Reserved Words - https://dev.mysql.com/doc/mysqld-version-reference/en/keywords-8-0.html [3]How to Fix the MySQL 1064 Error (5 Methods) - https://kinsta.com/knowledgebase/mysql-error-1064/#how-to-fix-the-mysql-1064-error-5-methods [4] Alter Table Statement - https://dev.mysql.com/doc/refman/8.0/en/alter-table.html [5]MySQL 8.0 Reference Manual - https://dev.mysql.com/doc/refman/8.0/en/

Hope it helps and if it does, I would appreciate if answer can be accepted so that community can benefit for clarity when searching for similar enquiries in repost/aws guide..