Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to realize mobile access database failure self-healing". In the operation process of actual cases, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

For holidays, rare holidays, especially when you go out, you encounter several database alarms, and those alarms belong to the time when you have to deal with them, which really makes people angry, so I also think of some ways to eliminate and avoid this situation as much as possible.

In general, there are several strategies:

1)Lower the alarm threshold in advance during holidays, and then handle a wave in advance

2)In the middle of the holiday, proactive inspection analysis, at least in a controlled time to encounter problems in advance rather than emergency solution of temporary problems is much better.

3)Multi-person backup, usually this situation is more difficult, have to carry computers everywhere, but also have to pay attention to computer power, network

Of course, there are also some mechanisms that can be used for reference. Generally, there are also two types:

1)For some usually controllable processing problems, periodic tasks can be set to process in advance, such as the binlog of the database grows faster, periodic tasks can be set to clean up, usually customized, and the localization degree is higher.

2)For foreseeable problems, action scripts can be set up to deal with them, and then periodic scans can be made to trigger the treatment mechanism once the problem is discovered, so this pattern is usually a periodic alternation of alarm/alarm recovery.

Of course, these strategies are not the best policy. After all, they are not universal enough. Sometimes the problems are different and need to be handled differently.

For example, disk alarm, if the disk alarm in 80%, then the problem is not so high urgency, processing mechanism priority disk space can be handled best, if it reaches 90%, disk space cleaning improvement space is very limited, you need to clean up database logs, etc., if continue to grow the urgency of the problem will gradually escalate, you need to access business logic, starting from some log table data.

In most cases, system space cleanup and binlog cleanup can slow down further escalation of problems, so it is rare to buffer for a few hours.

The access to the mobile terminal is also integrated after in-depth communication with development colleagues. This is a set of functional modules that have been running stably for a long time. In this respect, we are relatively late to access.

The mobile terminal handles disk alarms. The processing flow defined by me is as follows:

After the alarm is triggered, each processing action can be processed on the mobile side, and the corresponding API and script will be called on the backend to return the corresponding data parameters.

In the whole process, the definition of alarm category and the arrangement of processing flow are relatively core steps.

The most granular is the definition of each processing action.

After that, he could basically go out with peace of mind. After receiving the temporary alarm, his heart would also be calm.

Either way, this is a good start to self-healing.

"How to realize mobile access database failure self-healing" content is introduced here, thank you for reading. If you want to know more about industry-related knowledge, you can pay attention to the website. Xiaobian will output more high-quality practical articles for everyone!

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.