CN106933545B - Application system and start protection method and device thereof - Google Patents
Application system and start protection method and device thereof Download PDFInfo
- Publication number
- CN106933545B CN106933545B CN201511004993.0A CN201511004993A CN106933545B CN 106933545 B CN106933545 B CN 106933545B CN 201511004993 A CN201511004993 A CN 201511004993A CN 106933545 B CN106933545 B CN 106933545B
- Authority
- CN
- China
- Prior art keywords
- data
- application system
- starting
- dependent
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4418—Suspend and resume; Hibernate and awake
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides an application system and a start protection method and device thereof, wherein the method comprises the following steps: after a first application system initiates a request for acquiring and starting dependent data to a second system, judging whether the dependent data returned by the second system aiming at the request is received within a set time range; if the dependent data are received within the set time range, judging whether the dependent data conform to a preset data format; if the dependency data do not conform to the preset data format or if the dependency data are not received within the set time range, calling the pre-stored corresponding data loaded by the last successful start of the first application system for loading when the first application system is started at this time. The method and the device for starting the application system can improve the starting success rate of the application system.
Description
Technical Field
The present application relates to the field of system start technologies, and in particular, to an application system and a start protection method and apparatus thereof.
Background
Most current application systems are typically composed of multiple sub-service clusters. For example, one application system may include: the system comprises a user-related subsystem, a transaction-related subsystem, an accounting-related subsystem and the like, and meanwhile, resource files with certain universality can be uniformly stored, for example, all the files are centrally stored in the file subsystems and the like. As shown in fig. 1, when an application starts, it is likely to rely on a number of external data, such as: data provided by other application systems, some configuration information stored in a Database (DB), and some file data in a file system, etc. Therefore, the application system can start and provide corresponding business services normally only after acquiring the dependent external data.
In practical applications, the application system may be failed to start due to some reasons (such as network jitter, environmental problems, and other competing resources of the system), and especially, the failure to start due to long-time network outage of the network, DB down, unexpected data change, and the like, may directly affect the online business service of the application system.
Although many systems often adopt a redundancy design to improve the reliability of the system, for example, the DB often provides a main cluster + standby cluster; for a file system, multiple copies of data are stored to different nodes from time to time, and when one node fails, the other node can be switched to; for the application system, a cluster mode is often adopted to provide services, when one subsystem is abnormal, the subsystem is offline, and other normal subsystems provide services instead.
However, the inventors of the present application have found that even if these DBs, file systems, are used, it may be difficult to avoid a startup failure of the application system. This is because inter-system network jitter (e.g., sporadic network jitter between the application system and the DB) may not or not be enough to trigger the switch between the primary and the backup, and furthermore, when the DB, the file system or the underlying application service is normal, but the data that the application system provided by the DB depends on for starting is wrong or missing (e.g., some wrong data is accidentally operated into the DB by the database administrator, or some files are accidentally deleted due to a bug, etc.), the start of the application system at the upper layer still fails.
Disclosure of Invention
An object of the embodiments of the present application is to provide an application system and a start protection method and apparatus thereof, so as to improve a success rate of starting the application system.
In order to achieve the above object, in one aspect, an embodiment of the present application provides an application system start protection method, including the following steps:
after a first application system initiates a request for acquiring and starting dependent data to a second system, judging whether the dependent data returned by the second system aiming at the request is received within a set time range;
if the dependent data are received within the set time range, judging whether the dependent data conform to a preset data format;
if the dependency data do not conform to the preset data format or if the dependency data are not received within the set time range, calling the pre-stored corresponding data loaded by the last successful start of the first application system for loading when the first application system is started at this time.
On the other hand, an embodiment of the present application further provides an application system start-up protection device, including:
the data receiving module is used for judging whether the dependent data returned by the second system aiming at the request is received in a set time range after the first application system initiates a request for acquiring and starting the dependent data to the second system;
the format judging module is used for judging whether the dependent data conforms to a preset data format or not when the data receiving module receives the dependent data within the set time range;
and the first starting coordination module is used for calling the pre-stored corresponding data loaded by the last successful starting of the first application system when the dependent data does not conform to the preset data format or the data receiving module does not receive the dependent data within the set time range, so that the corresponding data can be loaded when the first application system is started at this time.
In another aspect, an embodiment of the present application further provides an application system, which includes the above-mentioned application system start-up protection device.
In the embodiment of the application, after a first application system initiates a request for acquiring and starting dependent data to a second system, whether the dependent data returned by the second system for the request is received within a set time range is judged; if the dependency data is not received within the set time range or the dependency data is received within the set time range but the format of the dependency data has a problem, calling the pre-stored corresponding data loaded by the last successful start of the first application system for loading when the first application system is started at this time. Because the corresponding data loaded by the last successful start of the application system is correct, even if the problems of network disconnection, downtime, network jitter or depending on data format errors and the like occur between the current application system and other related systems, the embodiment of the application can still ensure that the correct data which is depended on by the start can be loaded by the application system when the application system is started, thereby improving the success rate of the start of the application system.
Drawings
The accompanying drawings, which are included to provide a further understanding of the embodiments of the disclosure, are incorporated in and constitute a part of this disclosure. In the drawings:
FIG. 1 is a block diagram of a cluster system in the prior art;
fig. 2 is a flowchart of an application system boot protection method according to an embodiment of the present application;
fig. 3 is a block diagram illustrating an application system start-up protection device according to an embodiment of the present application;
fig. 4 is a block diagram of an application system start-up protection device according to another embodiment of the present application;
fig. 5 is a block diagram of an application system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application are described in further detail below with reference to the embodiments and the accompanying drawings. The exemplary embodiments and descriptions of the embodiments are provided to explain the embodiments and should not be construed as limiting the embodiments.
The following describes embodiments of the present application in further detail with reference to the accompanying drawings.
Referring to fig. 2, the application system start-up protection method according to the embodiment of the present application includes the following steps:
step S101, after a first application system initiates a request for acquiring and starting the dependent data to a second system, receiving the dependent data returned by the second system aiming at the request.
In the embodiment of the present application, the second system includes a second application system (i.e. other application system relative to the first application system), a file system and/or a database, etc. In addition, both the first application system and the second system in the embodiment of the present application may be a stand-alone system, or may be a clustered system (such as a distributed system).
In the embodiment of the present application, the startup dependent data described herein refers to dependent data stored in other systems that are required by the application system at the time of startup. For example, assume that the first application system is a, and when starting, it needs to acquire data B from the second application system B, data C from the file system C, and data D from the database D, in addition to the data a (such as some configuration information) that is stored by itself and depends on the start. If A initiates a request for calling the data depended on for starting to the second application system B, the data depended on for starting at the moment is B data, similarly, if A initiates a request for accessing the data depended on for starting to the file system C, the data depended on for starting at the moment is C data, and if A initiates a request for inquiring the data depended on for starting to the database D, the data depended on for starting at the moment is D data.
In the embodiment of the application, the time when the first application system initiates a request for acquiring the data relied for starting to the second system may be generally when the first application system is started; in addition, when the data depended on by the first application system in the second system for starting is updated, the first application system can also initiate a request for acquiring the data depended on by the starting to the second system.
And step S102, judging whether the dependency data returned by the second system aiming at the request is received in a set time range. If the dependency data returned by the second system for the request is received within a set time range, executing step S103; and if the dependency data returned by the second system for the request is not received within the set time range, executing step S104.
In this embodiment, the set time range may be a waiting time of the first application system after the request is issued. And the waiting time of the first application system after sending the request can be obtained by a notification mechanism and the like, and the notification mechanism can be realized by a callback function and the like.
And step S103, judging whether the dependent data conforms to a preset data format. Generally, the data format of the data relied on for starting is specified in the request for obtaining the data relied on for starting, which is initiated by the first application system to the second system. If the dependent data does not conform to the preset data format, step S104 is executed.
And step S104, calling the pre-stored corresponding data loaded by the last successful start of the first application system so as to load the first application system when the first application system is started at this time.
In the embodiment of the present application, the last successful start refers to the last successful start of the first application system. The last successful start of the first application system shows that the data loaded during the start is correct, and the application example returns the correct data to the first application system for the start loading of the first application system can certainly greatly improve the successful start probability of the first application system.
In other embodiments of the present application, if the dependency data conforms to the preset data format, the method for protecting the application system from starting may further include the following steps:
and step S105, comparing whether the dependency data is consistent with corresponding data loaded by the previous successful start of the first application system. If the dependency data is consistent with the corresponding data loaded by the previous successful start of the first application system, executing step S106; and if the dependent data is inconsistent with the corresponding data which is prestored and loaded by the last successful start of the first application system, executing the step S107.
In the embodiment of the present application, the corresponding data refers to: and the first application system may need to load multiple data at each starting, and one of the multiple data may be from the second system, so that the data from the second system is the corresponding data of the dependent data returned by the second system for the request. For example, the data x loaded by the last successful start of the first application system comes from the second system, and the dependent data in the response returned by the second system to the request this time is x ', so that the data x is the corresponding data of the data x ', that is, the comparison objects in this step are x and x '.
And S106, storing the dependent data, and marking the data loaded by the current start as the data loaded when the first application system is successfully started last time after the first application system finishes the start loading containing the dependent data. Wherein the saving is typically a local saving (e.g., saving to a local disk).
Step S107, storing the dependency data, and after the first application system finishes the starting and loading including the dependency data, checking whether the starting of the first application system is successful; wherein the saving is typically a local saving (e.g., saving to a local disk). If the starting of the first application system is successful, executing step S108; and if the starting of the first application system fails, skipping to execute the step S104, namely calling the pre-stored corresponding data loaded by the last successful starting of the first application system for the first application system to start and load again.
In the embodiment of the present application, the checking whether the current start of the first application system is successful may be a one-time detection. In another embodiment of the present application, the checking whether the current startup of the first application system is successful may further be checking whether the current startup of the first application system is successful for multiple times within a set time limit (for example, one hour after the first application system completes the startup loading including the dependency data), otherwise, the current startup of the first application system is considered as a failure. In some embodiments of the present application, the plurality of tests may be timed tests (e.g., tests performed every three minutes). In other embodiments of the present application, the plurality of tests may be random tests.
In addition, in the embodiment of the present application, the content of the check may include whether the system port is normal, whether the system responds to the outside normally, and/or whether the system can provide normal service. In another embodiment of the present application, it may further be determined whether the first application system is normally started by an event marking manner, where the first application system performs event marking (for example, writing a file) after the first application system is normally started, and if the event marking is received within a set time after the first application system is started, it indicates that the first application system is successfully started, otherwise, it indicates that the first application system is failed to be started.
And step S108, marking the data loaded in the current starting as the data loaded in the latest successful starting.
In the embodiment of the application, the significance of storing the data loaded when the first application system is successfully started last time is to provide convenience for subsequent starting of the first application system. In an embodiment of the present application, data loaded at the time of successful startup of multiple historical versions may be retained at the same time, and when there is a new version of data stored, data of an expired version (i.e. the earliest version) may be deleted. Of course, in another embodiment of the present application, in order to prevent the memory resources from being excessively occupied by the historical load data, only a few (e.g., three) versions of the data loaded at the time of successful boot need be generally reserved.
In some embodiments of the present application, as an optimization measure, if the dependent data is inconsistent with the corresponding data loaded by the last successful start of the first application system, the dependent data may be further marked as problem data and saved. The method aims to directly identify the data as problem data if the same data is received when the first application system initiates a request for acquiring the data depended on by starting to the second system next time, and the data is not preloaded so as to avoid wasting system resources. In other embodiments of the present application, if the dependent data is different from the corresponding data loaded by the last successful start of the first application system, the dependent data may also be directly deleted, so as to save the storage space.
While the process flows described above include operations that occur in a particular order, it should be appreciated that the processes may include more or less operations that are performed sequentially or in parallel (e.g., using parallel processors or a multi-threaded environment).
In the embodiment of the application, after a first application system initiates a request for acquiring and starting dependent data to a second system, whether the dependent data returned by the second system for the request is received within a set time range is judged; if the dependency data is not received within the set time range or the dependency data is received within the set time range but the format of the dependency data has a problem, calling the pre-stored corresponding data loaded by the last successful start of the first application system for loading when the first application system is started at this time. Because the corresponding data loaded by the last successful start of the application system is correct, even if the problems of network disconnection, downtime, network jitter or depending on data format errors and the like occur between the current application system and other related systems, the embodiment of the application can still ensure that the correct data which is depended on by the start can be loaded by the application system when the application system is started, thereby improving the success rate of the start of the application system.
In addition, if the dependency data received in the set time range conform to the preset data format, comparing whether the dependency data is consistent with the corresponding data loaded by the previous successful start of the first application system. If the data are consistent, the dependent data are saved and directly loaded; if not, the dependent data is stored, and whether the starting of the first application system is successful or not is checked after the first application system finishes the starting loading containing the dependent data. If the startup is successful, the data loaded by the startup is marked as the data loaded when the startup is successfully started last time. If the first application system fails, the pre-stored corresponding data loaded by the last successful start of the first application system is called, so that the first application system can be started and loaded again. Therefore, even if the content of the dependent data returned by other related systems has errors or is missing, the embodiment of the application can still ensure that the application system can be loaded with correct starting dependent data when being started, thereby further improving the starting success rate of the application system.
Referring to fig. 3, an application system start-up protection device according to an embodiment of the present application includes:
the data receiving module 31 is configured to determine whether to receive the dependent data returned by the second system for the request within a set time range after the first application system initiates a request for acquiring and starting the dependent data to the second system.
In the embodiment of the present application, the second system includes a second application system (i.e. other application system relative to the first application system), a file system and/or a database, etc. In addition, both the first application system and the second system in the embodiment of the present application may be a stand-alone system, or may be a clustered system (such as a distributed system).
In the embodiment of the present application, the startup dependent data described herein refers to dependent data stored in other systems that are required by the application system at the time of startup. For example, assume that the first application system is a, and when starting, it needs to acquire data B from the second application system B, data C from the file system C, and data D from the database D, in addition to the data a (such as some configuration information) that is stored by itself and depends on the start. If A initiates a request for calling the data depended on for starting to the second application system B, the data depended on for starting at the moment is B data, similarly, if A initiates a request for accessing the data depended on for starting to the file system C, the data depended on for starting at the moment is C data, and if A initiates a request for inquiring the data depended on for starting to the database D, the data depended on for starting at the moment is D data.
In the embodiment of the application, the time when the first application system initiates a request for acquiring the data relied for starting to the second system may be generally when the first application system is started; in addition, when the data depended on by the first application system in the second system for starting is updated, the first application system can also initiate a request for acquiring the data depended on by the starting to the second system.
In the embodiment of the application, the time when the first application system initiates a request for acquiring the data relied for starting to the second system may be generally when the first application system is started; in addition, when the data depended on by the first application system in the second system for starting is updated, the first application system can also initiate a request for acquiring the data depended on by the starting to the second system.
In this embodiment, the set time range may be a waiting time of the first application system after the request is issued. And the waiting time of the first application system after sending the request can be obtained by a notification mechanism and the like, and the notification mechanism can be realized by a callback function and the like.
The format determining module 30 is configured to determine whether the dependent data conforms to a preset data format when the data receiving module 31 receives the dependent data within the set time range. Generally, the data format of the data relied on for starting is specified in the request for obtaining the data relied on for starting, which is initiated by the first application system to the second system.
The first starting coordination module 32 is configured to, when the dependent data does not conform to the preset data format or the data receiving module 31 does not receive the dependent data within the set time range, call the pre-stored corresponding data loaded by the last successful start of the first application system, so that the corresponding data is loaded when the first application system is started this time.
The last successful start of the first application system shows that the data loaded during the start is correct, and the application example returns the correct data to the first application system for the start loading of the first application system can certainly greatly improve the successful start probability of the first application system.
In other embodiments of the present application, the application system start-up protection device may further include:
and a data comparison module 33, configured to, when the dependency data conforms to the preset data format, compare whether the dependency data is consistent with corresponding data that is pre-stored and loaded by the last successful start of the first application system.
In the embodiment of the present application, the corresponding data refers to: and the first application system may need to load multiple data at each starting, and one of the multiple data may be from the second system, so that the data from the second system is the corresponding data of the dependent data returned by the second system for the request. For example, the data x loaded by the last successful start of the first application system comes from the second system, and the dependent data in the response returned by the second system to the request this time is x ', so that the data x is the corresponding data of the data x ', that is, the comparison objects in this step are x and x '.
A second starting coordination module 35, configured to store the dependency data when the dependency data is inconsistent with corresponding data that is pre-stored and loaded in a last successful start of the first application system. Wherein the saving is typically a local saving (e.g., saving to a local disk).
A health check module 36, configured to check whether the current startup of the first application system is successful after the first application system completes the startup loading including the dependency data.
In the embodiment of the present application, the checking whether the current start of the first application system is successful may be a one-time detection. In another embodiment of the present application, the checking whether the current startup of the first application system is successful may further be checking whether the current startup of the first application system is successful for multiple times within a set time limit (for example, one hour after the first application system completes the startup loading including the dependency data), otherwise, the current startup of the first application system is considered as a failure. In some embodiments of the present application, the plurality of tests may be timed tests (e.g., tests performed every three minutes). In other embodiments of the present application, the plurality of tests may be random tests.
In addition, in the embodiment of the present application, the content of the check may include whether the system port is normal, whether the system responds to the outside normally, and/or whether the system can provide normal service. Since the above-mentioned inspection is a matter of routine skill in the art, it is not necessary to describe herein in detail. In another embodiment of the present application, it may further be determined whether the first application system is normally started by an event marking manner, where the first application system performs event marking (for example, writing a file) after the first application system is normally started, and if the event marking is received within a set time after the first application system is started, it indicates that the first application system is successfully started, otherwise, it indicates that the first application system is failed to be started.
A third starting coordination module 37, configured to, when the current starting of the first application system fails, call pre-stored corresponding data loaded by the last successful starting of the first application system, so as to allow the first application system to be restarted and loaded.
A fourth start coordination module 34, configured to, when the dependency data is consistent with corresponding data that is pre-stored and loaded in a last successful start of the first application system, store the dependency data, and after the first application system completes a start load that includes the dependency data, mark data loaded in the current start as data loaded in a last successful start. Wherein the saving is typically a local saving (e.g., saving to a local disk).
The first data marking module 38 is configured to mark, when the current start of the first application system is successful, the data loaded by the current start as the data loaded when the current start is successful.
In the embodiment of the application, the significance of storing the data loaded when the first application system is successfully started last time is to provide convenience for subsequent starting of the first application system. In an embodiment of the present application, data loaded at the time of successful startup of multiple historical versions may be retained at the same time, and when there is a new version of data stored, data of an expired version (i.e. the earliest version) may be deleted. Of course, in another embodiment of the present application, in order to prevent the memory resources from being excessively occupied by the historical load data, only a few (e.g., three) versions of the data loaded at the time of successful boot need be generally reserved.
And a second data marking module 39, configured to mark the dependent data as problem data when the current start of the first application system fails. In some embodiments of the present application, as an optimization measure, if the dependent data is inconsistent with the corresponding data loaded by the last successful start of the first application system, the dependent data may be further marked as problem data and saved. The method aims to directly identify the data as problem data if the same data is received when the first application system initiates a request for acquiring the data depended on by starting to the second system next time, and the data is not preloaded so as to avoid wasting system resources.
In another embodiment of the present application, as shown in fig. 4, the second data marking module 39 of the application system start-up protection device may be replaced with a data deleting module 39' without changing other modules. The data deleting module 39' is configured to delete the dependent data when the current start of the first application system fails, so as to save a storage space.
In the embodiment of the application, after a first application system initiates a request for acquiring and starting dependent data to a second system, a data receiving module judges whether the dependent data returned by the second system aiming at the request is received within a set time range; if the dependency data is not received within the set time range or the dependency data is received within the set time range but the format of the dependency data is in a problem, the first starting coordination module calls the pre-stored corresponding data loaded by the last successful starting of the first application system so as to load the first application system when the first application system is started at this time. Because the corresponding data loaded by the last successful start of the application system is correct, even if the problems of network disconnection, downtime, network jitter or depending on data format errors and the like occur between the current application system and other related systems, the embodiment of the application can still ensure that the correct data which is depended on by the start can be loaded by the application system when the application system is started, thereby improving the success rate of the start of the application system.
In addition, if the dependency data received in the set time range conform to the preset data format, the data comparison module compares whether the dependency data is consistent with the corresponding data loaded by the pre-stored last successful start of the first application system. If the data are consistent, the fourth starting coordination module saves the dependent data and directly loads the dependent data; and if not, the second starting coordination module stores the dependent data and checks whether the starting of the first application system is successful or not after the first application system finishes the starting loading containing the dependent data. If the data loading is successful, the first data marking module marks the data loaded by the current starting as the data loaded when the starting is successful last time. If the first application system fails, the third starting coordination module calls the pre-stored corresponding data loaded by the last successful starting of the first application system so as to be used for the first application system to start and load again. Therefore, even if the content of the dependent data returned by other related systems has errors or is missing, the embodiment of the application can still ensure that the application system can be loaded with correct starting dependent data when being started, thereby further improving the starting success rate of the application system.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, the functionality of the various modules may be implemented in the same one or more software and/or hardware implementations as the present application.
The device can be arranged in an application system as a part of the application system to realize the function of the application system. As another embodiment, the above apparatus may also be independently disposed between the first application system and the second system to implement its functions.
Referring to fig. 5, the application system of the embodiment of the present application is provided with an application system start-up protection device based on an original module, that is, the application system start-up protection device forms a part of the application system of the embodiment of the present application, and the application system start-up protection device interacts with the original module and a local disk of the application system to implement its function (for example, interacts with the local disk when data is stored, interacts with the original module of the application system when data is returned, and so on). Specifically, please refer to the above device embodiments, which are not described herein again.
The methods or apparatus described above in the embodiments of the present application may be embodied directly in a software module that is executable by a processor. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
Those of skill would further appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein may be implemented as a combination of hardware and software, such as by implementing portions of the spectral analysis of the embodiments disclosed herein in hardware while other portions are implemented in software. Whether implemented in software or a combination of software and hardware depends upon the particular application and design requirements of the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present application in further detail, and it should be understood that the above-mentioned embodiments are only examples of the embodiments of the present application and are not intended to limit the scope of the present application, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present application should be included in the scope of the present application.
Claims (11)
1. An application system start protection method is applied to a first application system and comprises the following steps:
after a first application system initiates a request for acquiring and starting dependent data to a second system, judging whether the dependent data returned by the second system aiming at the request is received within a set time range; the starting dependent data refers to dependent data which is required by the first application system when the first application system is started and is stored in the second system;
if the dependent data are received within the set time range, judging whether the dependent data conform to a preset data format or not, and judging whether the dependent data are prestored problem data or not, wherein the problem data are the dependent data corresponding to the failed starting;
if the dependent data do not conform to the preset data format, or the dependent data are problem data, or if the dependent data are not received within the set time range, calling the pre-stored corresponding data loaded by the last successful start of the first application system for loading when the first application system is started at this time;
if the dependent data conform to the preset data format and the dependent data do not belong to problem data, comparing whether the dependent data are consistent with corresponding data loaded by the previous successful start of the first application system and prestored;
if the dependency data is inconsistent with the corresponding data loaded by the previous successful start of the first application system, the dependency data is stored, and whether the start of the first application system is successful or not is checked after the first application system finishes the start and the load containing the dependency data;
if the starting of the first application system fails, calling the pre-stored corresponding data loaded by the last successful starting of the first application system so as to be used for the first application system to start and load again.
2. The application system boot protection method of claim 1, further comprising:
and if the first application system is successfully started at this time, marking the data loaded by the starting at this time as the data loaded when the starting is successfully started at the last time.
3. The method for protecting the startup of the application system according to claim 1, further comprising, when the current startup of the first application system fails:
deleting the dependent data or marking the dependent data as problem data.
4. The method for protecting the startup of the application system according to claim 1, wherein the step of checking whether the startup of the first application system is successful comprises:
and checking whether the starting of the first application system is successful or not for multiple times within a set time limit.
5. The application system boot protection method of claim 1, wherein the second system comprises a second application system, a file system, and/or a database.
6. An application system start-up protection device, which is applied to a first application system, comprises:
the data receiving module is used for judging whether the dependent data returned by the second system aiming at the request is received in a set time range after the first application system initiates a request for acquiring and starting the dependent data to the second system; the starting dependent data refers to dependent data which is required by the first application system when the first application system is started and is stored in the second system;
the format judging module is used for judging whether the dependent data conforms to a preset data format or not and judging whether the dependent data is prestored problem data or not when the data receiving module receives the dependent data within the set time range, wherein the problem data is the dependent data corresponding to the failed starting;
the first starting coordination module is used for calling the pre-stored corresponding data loaded by the last successful starting of the first application system when the dependent data does not conform to the preset data format, or the dependent data is problem data, or the data receiving module does not receive the dependent data within the set time range, so that the corresponding data can be loaded when the first application system is started at this time;
the data comparison module is used for comparing whether the dependency data are consistent with corresponding data loaded by the last successful start of the pre-stored first application system or not when the dependency data conform to the preset data format and the dependency data do not belong to problem data;
the second starting coordination module is used for saving the dependency data when the dependency data is inconsistent with corresponding data which is prestored and loaded by the last successful starting of the first application system;
the health check module is used for checking whether the starting of the first application system is successful or not after the first application system finishes the starting and loading including the dependency data;
and the third starting coordination module is used for calling the pre-stored corresponding data loaded by the last successful starting of the first application system when the current starting of the first application system fails so as to allow the first application system to be started and loaded again.
7. The application startup protection device of claim 6, further comprising:
and the first data marking module is used for marking the data loaded by the current starting as the data loaded when the current starting of the first application system is successful.
8. The application startup protection device of claim 6, further comprising:
the data deleting module is used for deleting the dependent data when the starting of the first application system fails;
or, the second data marking module is configured to mark the dependent data as problem data when the current start of the first application system fails.
9. The device as claimed in claim 6, wherein the health check module checks whether the current start of the first application system is successful, comprising:
and checking whether the starting of the first application system is successful or not for multiple times within a set time limit.
10. The application system startup protection device of claim 6, wherein the second system comprises a second application system, a file system, and/or a database.
11. An application system, characterized in that it comprises an application system start-up protection device according to any one of claims 6 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511004993.0A CN106933545B (en) | 2015-12-29 | 2015-12-29 | Application system and start protection method and device thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511004993.0A CN106933545B (en) | 2015-12-29 | 2015-12-29 | Application system and start protection method and device thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106933545A CN106933545A (en) | 2017-07-07 |
| CN106933545B true CN106933545B (en) | 2020-09-29 |
Family
ID=59458222
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511004993.0A Active CN106933545B (en) | 2015-12-29 | 2015-12-29 | Application system and start protection method and device thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106933545B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108595948A (en) * | 2018-04-19 | 2018-09-28 | 深圳鼎智通讯股份有限公司 | A kind of Android intelligence POS terminal prepackage APP and its means of defence |
| CN111722886A (en) * | 2020-06-23 | 2020-09-29 | 平安医疗健康管理股份有限公司 | Tool starting method and device, computer equipment and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101894032A (en) * | 2010-06-30 | 2010-11-24 | 中兴通讯股份有限公司 | Method for starting software system of base station, base station and master single board in base station |
| CN102591866A (en) * | 2011-01-06 | 2012-07-18 | 中国移动通信有限公司 | Method, device and system for starting browser |
| CN103500128A (en) * | 2013-09-30 | 2014-01-08 | 上海斐讯数据通信技术有限公司 | NVRAM data backup method |
| CN103516668A (en) * | 2012-06-20 | 2014-01-15 | 中国银联股份有限公司 | Broadcast-type database reconnection-based data processing server and broadcast-type database reconnection method |
| CN104636165A (en) * | 2015-02-02 | 2015-05-20 | 广东小天才科技有限公司 | Mobile device starting method and device |
-
2015
- 2015-12-29 CN CN201511004993.0A patent/CN106933545B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101894032A (en) * | 2010-06-30 | 2010-11-24 | 中兴通讯股份有限公司 | Method for starting software system of base station, base station and master single board in base station |
| CN102591866A (en) * | 2011-01-06 | 2012-07-18 | 中国移动通信有限公司 | Method, device and system for starting browser |
| CN103516668A (en) * | 2012-06-20 | 2014-01-15 | 中国银联股份有限公司 | Broadcast-type database reconnection-based data processing server and broadcast-type database reconnection method |
| CN103500128A (en) * | 2013-09-30 | 2014-01-08 | 上海斐讯数据通信技术有限公司 | NVRAM data backup method |
| CN104636165A (en) * | 2015-02-02 | 2015-05-20 | 广东小天才科技有限公司 | Mobile device starting method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106933545A (en) | 2017-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106716972B (en) | Semi-automatic failover | |
| CN106533805B (en) | Micro-service request processing method, micro-service controller and micro-service architecture | |
| JP2003256225A (en) | Computer system, failure countermeasure and program for making computer system function | |
| CN109788068B (en) | Heartbeat state information reporting method, device and equipment and computer storage medium | |
| US9880897B2 (en) | Failure mode identification and reporting | |
| CN107508694B (en) | Node management method and node equipment in cluster | |
| US7730029B2 (en) | System and method of fault tolerant reconciliation for control card redundancy | |
| CN109634638B (en) | Cluster software upgrading method, device, equipment and medium | |
| CN103036706A (en) | Local processing method of application upgrading abnormity | |
| CN113434337B (en) | Retry strategy control method and device and electronic equipment | |
| CN106933545B (en) | Application system and start protection method and device thereof | |
| WO2020211362A1 (en) | Method and apparatus for improving availability of trunking system, and computer device | |
| US9465643B1 (en) | Systems and methods for monitoring a primary operating system (OS) and/or migrating data using an OS hypervisor | |
| US10372682B2 (en) | Maintaining data integrity | |
| CN106909410B (en) | Updating method for server system and server system | |
| US8639227B1 (en) | Providing digital content usability for a mobile device user | |
| CN111209197B (en) | Application continuous integration test method, system, equipment and storage medium | |
| CN109672573B (en) | Configuration file deployment method, configuration file determination method, server and storage medium | |
| CN109510867B (en) | Data request processing method and device, storage medium and electronic equipment | |
| CN111614701B (en) | Distributed cluster and container state switching method and device | |
| CN115686951A (en) | Fault processing method and device for database server | |
| EP3070610B1 (en) | Information processing device, control method thereof, and recording medium | |
| CN111367885A (en) | Database management system, database management method, storage medium, and electronic device | |
| CN111159786B (en) | Metadata protection method and device, electronic equipment and storage medium | |
| CN113778753B (en) | Method, device, equipment and medium for automatically correcting database after storage recovery |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: Greater Cayman, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |