About the database of master-slave, and what's more mature plan now
For example, to upgrade project, now I need to execute SQL update table structure and data
How can the user has no sense to upgrade?
We are nginx + + mysql, tomcat is a Java web project
The database upgrade, tomcat, table structure changes will lead to page 500
So consider is the use of the cluster, stop for machine upgrade and start for the host upgrade
The problem is that now the mysql cluster solution, using which approach is better?
Before the two test environment to run the mysql server, made of the replication double master replicate
May be the trigger, timing task, causes of the stored procedure did run after a period of time is one of the data cannot operation, lead to can't synchronous fault
Everyone in the practical work is to use what kind of way
configuration of the cluster?
Before I thought of the following ways, it is the replication way of
Main master replicate, two is the host, reading and writing are available
Master-slave replication, reading and writing separate
Master-slave replication, host provides reading and writing, from the backup machine only
Please use master in the practical work of master replicate, if configured properly, the master replicate whether can into production,
Experienced friend to give answers
CodePudding user response:
In addition, our online mysql environment is 5.6, consider later upgraded to 5.7 or 8.0