Shulou(Shulou.com)06/02 Report--

This article introduces MYSQL Group replication Crash quick recovery method is how, the content is very detailed, interested friends can refer to, hope to help everyone.

Recently, after detecting the developed statements, it was found that some statements had problems that were not optimized at all. The root cause of MYSQL system optimization was that the customer's requirements were too strange.

To what extent, it is required to display more than 2 million pieces of data after each startup page. This is the problem I found after detecting and optimizing the statement, and asked the developer. The developer told me that since the customer did not understand IT technology, according to his own ideas, and thought it was not difficult.

Personal point of view, such customers our guidance, education, although in the 21st century, or to allow some people do not understand the logic of IT, after all, people are not doing this work, which requires the depth and breadth of our work.

Well, back to the topic, how to quickly repair after MGR crash, the method here is first of all fast and stable, and can cope with any environment. Of course, since the method was so good, it must have its limitations.

How bad is the system? This system was originally a test, but the system that was set up on this system was about to go online when it was tested, and because the testers were also testing, the test system became less "tested". If it broke down, there would be many people challenging you.

The specific process is like this. Due to the stress test requirements, the memory on this machine has already started to use SWAP. In fact, there is still a communication with the operation and maintenance personnel here, that is, they think that if the memory exchange is not frequent from the virtual machine, it means that there is no shortage of memory. I personally do not agree with this point of view, first of all, the database and other infrastructure is not the same, memory must be rich, another problem is that the database is the reason for their own HOLD memory, even MYSQL so many systems and memory management are handed over to LINUX system things or willing to H live more memory.

Although it is a virtual machine, but add memory or shut down,(how I remember, virtual machine add memory should be online), of course, if online add, there will be no this paragraph and this text.

After shutting down the clustered machines, adding memory, starting MYSQL, redoing the initialization of the cluster, and adding another machine to the cluster, an error was reported in the process of adding another machine.

Attempts to re-add machines to the cluster failed. Here the fastest way, backup in the means of recovery, select one of the machines for backup, backup after the data has been restored to the damaged machine, restart the machine, but still error.

The error message is as above. After seeing the problem of repeated execution of GTID, stop copying directly on the corresponding library, then reset the host information, and then reset gtid_purged (relevant information is found in the backup). then

Restart cluster join node

The relevant machines have returned to the cluster and started working

The repair process seems simple, but in fact, in order to find other methods and in fact, the process is tortuous and bad (not to mention here). Fortunately, before starting work in the morning, this matter was over, otherwise it would be a very sad day.

About MYSQL Group replication Crash quick recovery method is how to share here, I hope the above content can be of some help to everyone, you can learn more knowledge. If you think the article is good, you can share it so that more people can see it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.