A lot of things, as long as good break down into tiny steps, write down write clearly solved.
For example, the index line synchronization heat order to switch from the old program to the new queue order non-sequential program queue. Because of this concern has been synchronized index is very sensitive, and not sure about some of the key steps have been dragging did not do it. Until a problem, it is determined to resolve it. In fact, not so difficult.
One problem: the sensitivity of solving
As the buyer orders, payment orders after the completion of the search, priority will be routed to the heat index, so the index synchronization delay is very sensitive. Improper operation, or there are unexpected circumstances, can easily lead to synchronization delay or error, the first time the impact to the buyer, the merchant, or even cause a malfunction.
Countermeasures: to operate in the early morning. At this point, most of the merchants, buyers have to sleep, nature would not have been delayed or temporarily synchronization errors are perceived to be more boldly executed. You see, it's that simple! Of course, a little too hard.
Second problem: the key steps are not sure
To make it clear overall process, a key step in determining not sure, I do not know where the point? Ask an experienced junior partner, to find out.
Tip: Refinement
After the process step of the overall figure, each point thinning.
- Such as message observe whether the accumulation channel, put the address of the message interface system to write clearly, specific operation, it can be written in accordance with.
- For example, task switching, which the old synchronization task to close, what to observe, such as how long, and then open a new synchronization task. Write operation can be clearly enough.
- For example, a list of the checkpoint after the switch, if there is an error log, log normal consumption is OK, is there a message accumulation of orders after the orders search is OK, sync monitor is OK and so on.