Support Questions

Find answers, ask questions, and share your expertise

Cloudera cluster impact of Mysql RDS 5.6 to 5.7 Upgrade

avatar
New Contributor

Hello , 

 

Amazon RDS is starting the end of life (EOL) process for MySQL major version 5.6 .

 

Hence we are going to migrate Mysql 5.6 to 5.7 . Our CM/CDH Version is 5.11.2 .

What would be the impact of Mysql RDS Upgrade from 5.6 to 5.7 on the cloudera cluster ? Do we require any downtime on the cluster ?

1 ACCEPTED SOLUTION

avatar
Master Guru

@Ayyavaru Typically there is no external steps needed from CM side as CM only needs DB to be up so it depends on your plan honestly. However I would suggest you to take BACKUP of CM database for safe side [1] as well as plan downtime for this activity.

You can use mysqldump to back up databases without having to shut them database down (see https://dev.mysql.com/doc/refman/5.7/en/mysqldump-sql-format.html). However, to ensure you get a good back, you should make sure there is no activity. i.e. you can get the back up by stopping the Cloudera manager server or any service for the database you are backing up. We strongly encourage that you consult your DBA or database vendor. After that you have to check the db.properties is rightly pointed to the database configured for CM. Hope this helps. 

[1]https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_backup_dbs.html#concept_tyh_r...


Cheers!
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

View solution in original post

1 REPLY 1

avatar
Master Guru

@Ayyavaru Typically there is no external steps needed from CM side as CM only needs DB to be up so it depends on your plan honestly. However I would suggest you to take BACKUP of CM database for safe side [1] as well as plan downtime for this activity.

You can use mysqldump to back up databases without having to shut them database down (see https://dev.mysql.com/doc/refman/5.7/en/mysqldump-sql-format.html). However, to ensure you get a good back, you should make sure there is no activity. i.e. you can get the back up by stopping the Cloudera manager server or any service for the database you are backing up. We strongly encourage that you consult your DBA or database vendor. After that you have to check the db.properties is rightly pointed to the database configured for CM. Hope this helps. 

[1]https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_backup_dbs.html#concept_tyh_r...


Cheers!
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.