Mobile Survey and compensation version system on-line-docking claims failure, resulting in the case can not be issued and processed properly

Upgrade start time: 2017-5-4 19:00

Upgrade end time: 2017-5-4 22:00

2017-5-5-Friday:

A problem occurred:

Most of the branch feedback can not accept the compensation case, a small number of branch feedback to receive the case, but no survey information.

The actual reason: Before doing the upgrade operation, consider the poor result, only consider whether the branch needs to do operation, in addition to the pilot branch to do some operations, all operations are operated by the head office.

• The pilot branch needs to perform the operation:

1. Modify the configuration file parameters (the core corresponding F5 address) in the Access project package and restart the service

2, the branch office claims (self-compensation) related parameters modified to the production core address, and then restart the service

• Operations required by the head office:

1. Stop Mobile Survey all services

2, backup 5001 version corresponding project package, apk,csv file

3, upload 5002 version corresponding project package, apk,csv file

4, the implementation of research and development support provided by the modified Force upgrade version 5002 apk corresponding SQL statement

5, start a single managed node, view the running status, after the development of the correct, start all cluster managed nodes

omission not performed: the F5 address of the system needs to be inserted in the database for each branch user

Because of the omission of this step, resulting in the compensation can not be issued to each branch of the case.

Reflections on the accident and how to improve it:

Accident Reflection: The cause of the accident caused by poor consideration, the core factor is the operation and maintenance personnel on the overall process has been omitted, operation and maintenance still need to be strengthened.

How to improve in the future:

1. When there is a major upgrade change, write the upgrade timeline, similar to:

650) this.width=650; "src=" https://s3.51cto.com/wyfs02/M02/94/D5/wKiom1kO0HzSQPzxAAKqf-XU6ik449.jpg "title=" 1.jpg "alt=" Wkiom1ko0hzsqpzxaakqf-xu6ik449.jpg "/>

2, write the Runbook (run manual, that is, the operation of the procedure), that is, during the upgrade process, belongs to the part of our operation, we should do, to be very organized and logically describe our operating procedures, recommended in chronological order to write.

3, the time axis and the Runbook together to let the project team colleagues and leaders to look and comments.

This article from the "Breeze of the Month blog" blog, declined to reprint!

Mobile Survey and compensation version system on-line-docking claims failure, resulting in the case can not be issued and processed properly