CN116996365A - Service fault processing method, service fault processing device, electronic equipment and medium - Google Patents
Service fault processing method, service fault processing device, electronic equipment and medium Download PDFInfo
- Publication number
- CN116996365A CN116996365A CN202311073007.1A CN202311073007A CN116996365A CN 116996365 A CN116996365 A CN 116996365A CN 202311073007 A CN202311073007 A CN 202311073007A CN 116996365 A CN116996365 A CN 116996365A
- Authority
- CN
- China
- Prior art keywords
- service
- steady
- node combination
- target service
- information
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title abstract description 12
- 238000012545 processing Methods 0.000 title abstract description 8
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000008859 change Effects 0.000 claims description 16
- 230000002159 abnormal effect Effects 0.000 claims description 15
- 238000012790 confirmation Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 7
- 238000005096 rolling process Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 230000000007 visual effect Effects 0.000 description 11
- 238000012423 maintenance Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000011084 recovery Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 241000282414 Homo sapiens Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The disclosure provides a service fault processing method, a service fault processing device, electronic equipment and a computer readable storage medium, and belongs to the technical field of computers. The method comprises the following steps: responding to the failure of a target service, and acquiring steady-state node combination information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and according to the steady-state node combination information, carrying out data rollback on the service node in the target service. The method and the device can roll back the data quickly and accurately so as to restore the normal operation of the service.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service fault processing method, a service fault processing device, an electronic device, and a computer readable storage medium.
Background
With the rapid development of internet technology, in order to adapt to business demands and market changes, upgrade or update of system services related to computers is more and more frequent, and at the same time, higher requirements are also put on system stability and service reliability.
At present, the service can not normally operate due to problems such as faults and the like in the operation process. The prior art generally requires maintenance personnel to manually rollback data for a failed service by looking up the historical codes of the failed program in the service to restore normal operation of the service. However, in this way, on one hand, the accuracy of the history code lookup directly affects the accuracy of service rollback, and this way requires higher labor and time costs, and service recovery efficiency is lower, depending on more subjective operations by human beings; on the other hand, considering that there may be coupling or other dependencies between program code, rolling back data on a portion of code may not solve the problem of version compatibility with dependencies.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The disclosure provides a service fault processing method, a service fault processing device, an electronic device and a computer readable storage medium, so as to at least overcome the problems that the service fault processing in the prior art needs to consume higher labor cost and time cost and the rollback of data is easy to make mistakes to a certain extent.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to one aspect of the present disclosure, there is provided a service failure processing method including: responding to the failure of a target service, and acquiring steady-state node combination information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and according to the steady-state node combination information, carrying out data rollback on the service node in the target service.
In an exemplary embodiment of the present disclosure, before acquiring the steady-state node combination information of the target service, the method further includes: responding to the change of at least one service node in the target service, and combining the current service node in the target service after the change to generate a node combination to be confirmed; and when the node combination to be confirmed is determined to be stable, generating steady-state node combination information according to the information of the node combination to be confirmed.
In an exemplary embodiment of the disclosure, the obtaining steady-state node combination information of the target service includes: and acquiring steady-state node combination information of the target service with the latest generation time.
In an exemplary embodiment of the disclosure, the determining that the node to be validated is combined stable includes: and when the target service runs for a preset time period with the node combination to be confirmed and the abnormal condition of the target service does not occur, determining that the node combination to be confirmed is stable.
In an exemplary embodiment of the present disclosure, after generating the steady-state node combination information according to the information of the node combination to be confirmed, the method further includes: and canceling the generation of the steady-state node combination information in response to the discard operation of the steady-state node combination information.
In an exemplary embodiment of the present disclosure, the steady state node combination information includes a steady state node identification combination, and the determining the steady state node combination information according to the information of the node combination to be confirmed includes: and combining the identification information of each service node in the node combination to be confirmed to generate the steady-state node identification combination.
In an exemplary embodiment of the disclosure, the performing data rollback on the service node in the target service according to the steady node combination information includes: and responding to rollback confirmation operation, and performing data rollback on the service nodes in the target service according to the steady-state node combination information.
According to an aspect of the present disclosure, there is provided a service failure processing apparatus including: the combined information acquisition module is used for responding to the failure of the target service and acquiring the steady-state node combined information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and the data rollback module is used for rolling back the data of the service node in the target service according to the steady-state node combination information.
According to one aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the method of any of the above via execution of the executable instructions.
According to one aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one of the above.
Exemplary embodiments of the present disclosure have the following advantageous effects:
responding to the failure of the target service, and acquiring steady-state node combination information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and according to the steady-state node combination information, carrying out data rollback on the service nodes in the target service. On one hand, the present exemplary embodiment proposes a new service fault processing method, which performs overall data rollback on service nodes in a target service node through acquired steady-state node combination information of the target service, so as to avoid the situation that rollback is abnormal or incompatible due to the fact that information in the service has a dependency relationship; on the other hand, when the target service fails, the data rollback can be performed based on the steady-state node combination information, operation and maintenance personnel are not required to manually search historical code versions, the situation that errors occur in the data rollback due to searching errors is avoided, the accuracy of the data rollback can be improved, and labor cost and time cost can be reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 schematically shows a flowchart of a service failure processing method in the present exemplary embodiment;
fig. 2 schematically shows a sub-flowchart of a service failure processing method in the present exemplary embodiment;
FIG. 3 schematically illustrates a partial schematic view of a visual service management interface in the present exemplary embodiment;
fig. 4 schematically illustrates a partial schematic view of service fault recovery in a visual service management interface in the present exemplary embodiment;
fig. 5 schematically shows a topology diagram of service dependency in the present exemplary embodiment;
fig. 6 schematically shows a flowchart of another service failure processing method in the present exemplary embodiment;
fig. 7 schematically shows a block diagram of a service failure processing apparatus in the present exemplary embodiment;
fig. 8 schematically shows an electronic device for implementing the above method in the present exemplary embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Exemplary embodiments of the present disclosure first provide a service failure processing method. The following describes the present exemplary embodiment with reference to fig. 1, and as shown in fig. 1, the service fault handling method may include the following steps S110 to S120:
step S110, in response to the failure of the target service, acquiring steady-state node combination information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service.
The target service refers to a service to be processed in the present exemplary embodiment, which may be a service of any program, for example, a game playback service or a game video service, and the present exemplary embodiment may select one or more services from the system as the target service. The service failure refers to that the service cannot normally run, for example, when the service is updated or upgraded, and when the service is run, the service is stopped, an error log or an abnormal alarm occurs, and the like, the target service is considered to be failed. When the target service fails, steady-state node combination information of the target service can be further acquired; if the target service does not fail, no subsequent flows may need to be performed.
The target service may include a plurality of service nodes, where the service nodes refer to information such as execution modules or files related to running the service, for example, codes, dependency relationships, running environments, configuration, and the like, and the configuration may include a configuration module and a configuration file for executing information configuration. Different target services may have different service nodes, for example in the python technology stack, and a single service may include both service mirroring and service configuration service nodes. Thus, the present exemplary embodiment may acquire the technology stack of the target service first, and then confirm one or more service nodes included in the target service according to specific information of the technology stack. The node combination refers to the whole formed by combining different service nodes, for example, a "service image+service configuration" can be used as a node combination, the content and the number of the service nodes in the node combination can be adjusted according to actual needs, and the present exemplary embodiment can consider all the service nodes included in the target service as a whole as a node combination. The steady-state node combination information refers to information of the service node in a target service steady-state operation state, and the information can represent the state and version of each service node, for example, identification information of the service node combination in the steady-state operation state, such as representing a determined steady-state node batch by adopting a numerical identification, representing a determined steady-state node category by adopting a letter identification, or representing a determined steady-state node name by adopting an abbreviated identification; name information, such as configuring the first version, mirroring the first version, etc.; combining information such as combining the configuration first plate and the mirror image first plate; timestamp information, such as configuration (update at 12) +mirror (update at 13), and the like, as well as combinations of one or more of the specific information of the serving node. Wherein a steady operating state may be considered an operating state in the absence of a fault.
And step S120, carrying out data rollback on the service node in the target service according to the steady-state node combination information.
Further, the data rollback may be performed on each service node in the target service according to the steady state node combination information, specifically, which state or version each service node corresponding to rollback should correspond to may be determined according to the identification information of the steady state node combination, so that each service node in the target service is rolled back to the corresponding state or version, for example, the steady state node combination information is "configuration a+mirror image a", the service node of the current target service is configuration a and mirror image B, and then the service node in the target service may be rolled back to the state corresponding to "configuration a+mirror image a" according to the steady state node combination information, or the steady state node combination information is "configuration (update at 12) +mirror image (update at 13)", and then the service node in the target service is rolled back to the configuration updated at 12 and the state corresponding to the mirror image updated at 13.
Based on the above description, in the present exemplary embodiment, in response to a failure of a target service, steady-state node combination information of the target service is acquired; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and according to the steady-state node combination information, carrying out data rollback on the service nodes in the target service. On one hand, the present exemplary embodiment proposes a new service fault processing method, which performs overall data rollback on service nodes in a target service node through acquired steady-state node combination information of the target service, so as to avoid the situation that rollback is abnormal or incompatible due to the fact that information in the service has a dependency relationship; on the other hand, when the target service fails, the data rollback can be performed based on the steady-state node combination information, operation and maintenance personnel are not required to manually search historical code versions, the situation that errors occur in the data rollback due to searching errors is avoided, the accuracy of the data rollback can be improved, and labor cost and time cost can be reduced.
In an exemplary embodiment, as shown in fig. 2, before the steady-state node combination information of the target service is acquired, the service fault handling method may further include the following steps:
step S210, responding to the change of at least one service node in the target service, and combining the current service nodes in the target service after the change to generate a node combination to be confirmed;
step S220, when the node combination to be confirmed is determined to be stable, generating steady-state node combination information according to the information of the node combination to be confirmed.
The service node change may be a change or update of the service node, for example, upgrade or modify the service node, when at least one service node in the target service changes, the current service node in the target service may be combined after the change to generate a node combination to be confirmed, for example, the target service includes a service node combination of "mirror image 1+running environment 1+configuration 1" before the change, and after the mirror image 1 changes to the mirror image 2, the node combination to be confirmed is "mirror image 2+running environment 1+configuration 1"; or, after the mirror image 1 is changed to the mirror image 2 and the running environment 1 is changed to the running environment 2, the nodes to be confirmed are combined to be 'mirror image 2+running environment 2+configuration 1'.
When the node combination to be confirmed is determined to be stable, namely, when the target service normally operates with the node combination to be confirmed, the node combination to be confirmed can be determined to be a steady-state node combination, and further, steady-state node combination information can be generated according to the information of the node combination to be confirmed.
It should be noted that, in the running process of the target service, multiple service node changes may be performed, and the steady state node combination information may be updated along with the determination of the steady state node combination at different times. The present exemplary embodiment may perform data rollback using the steady state node combination information determined the last time, may perform data rollback using the steady state node combination information determined historically as needed, or the like, for example, according to which target time range the user wishes to rollback, determine steady state node combination information in the vicinity of its range according to the target time range, perform data rollback operation to restore the target service to the target state, or the like.
In an exemplary embodiment, in the step S220, determining that the node combination to be confirmed is stable may include:
and when the target service runs for a preset time period with the node combination to be confirmed and the abnormal condition of the target service does not occur, determining that the node combination to be confirmed is stable.
In this exemplary embodiment, the stability of the node combination to be confirmed means that when the target service runs with the node combination to be confirmed, no abnormal situation such as a fault occurs, and specifically, the judgment can be performed by a condition that the target service runs with the node combination to be confirmed for a preset period of time and the target service does not have an abnormal situation. The preset duration refers to a standard duration for judging whether the target service is running stably, and may be set in a user-defined manner according to specific needs, for example, the preset duration may be 12 hours, 24 hours, 48 hours, or the like, which is not specifically limited in the disclosure. When the target service runs for a preset time period with the node combination to be confirmed and no abnormal condition occurs in the target service, for example, after the code is updated or upgraded, the target service runs for one day with a new node combination to be confirmed, no error log occurs, or abnormal alarm occurs, the node combination to be confirmed is indicated to be a stable node combination, the stable node combination can be determined to be a stable node combination, stable node combination information is generated according to the information of the node combination to be confirmed, for example, identification information of all service nodes in the node combination to be confirmed is combined to be used as stable node combination information.
In this exemplary embodiment, one or more service nodes may change one or more times in the target service, so a plurality of time-corresponding node combinations to be confirmed may be generated based on the changed target service, and if it is determined that the node combinations to be confirmed are steady-state node combinations, a plurality of time-corresponding steady-state node combination information may be further generated. The present exemplary embodiment may include various manners when acquiring the steady-state node combination information of the target service, for example, according to the operation and maintenance personnel, the steady-state node combination information may be selected or set for a certain time according to the current requirement in a self-defining manner, so as to perform data rollback; or the system automatically selects default steady-state node combination information to roll back data; steady-state node combination information under a certain preset mechanism can be acquired to perform data rollback and the like.
In an exemplary embodiment, in the step S110, acquiring the steady-state node combination information of the target service may include:
and acquiring steady-state node combination information of the target service with the latest generation time.
In order to ensure the instantaneity and effectiveness of the steady-state node combination, the present exemplary embodiment may acquire steady-state node combination information of the target service with the latest generation time, for example, acquire a timestamp generated by each steady-state node combination, and select the steady-state node combination information with the timestamp closest to the current time as the steady-state node combination information of the target service.
In an exemplary embodiment, after generating the steady-state node combination information according to the information of the node combination to be confirmed, the service fault handling method may further include:
and canceling the generation of the steady-state node combination information in response to the discard operation of the steady-state node combination information.
The discard operation refers to a rejection operation of a steady-state node combination, which is input by a user or automatically triggered by a system according to the operation condition. In this exemplary embodiment, the target service may automatically confirm that the node to be confirmed is a steady-state node combination under the condition that the node to be confirmed stably operates for a preset period of time, so as to generate steady-state node combination information. In order to facilitate management of the steady-state node combination, specifically, whether the steady-state node combination is a valid steady-state node combination or whether it is necessary to determine a new steady-state node combination, for example, when an operator wants to reserve more previous steady-state node combinations, or in order to save memory space or save power consumption, it is not desirable to reserve too much steady-state node combination information, a discard operation may be performed on the generated steady-state node combination information by a manual/automatic triggering manner, that is, the present exemplary embodiment sets a rejection mechanism for the automatically confirmed steady-state node combination or the automatically generated steady-state node combination information, so as to ensure the accuracy and the validity of the determination of the steady-state node combination information. The method and the device can automatically confirm the stable node combination information based on the system, and judge whether to retain the stable node combination information based on manual operation or automatic triggering, so that the efficiency of generating the stable node combination information is improved, and the accuracy of generating the stable node combination information is ensured.
It should be noted that, when the operation of discarding the steady-state node combination information is performed, the current generated steady-state node combination information is cancelled. In order to ensure the normal operation of the data rollback, the historically determined steady state node combination information can be used as the basis of the data rollback, and the data rollback can be performed according to the historical steady state node combination, for example, if the i-th determined steady state node combination information is canceled, the data rollback can be performed according to the i-1-th determined steady state node combination information. In addition, if the steady state node combination information stored in the system is empty, for example, the steady state node combination information is not determined yet, when the user inputs the discard operation of the current determined steady state node combination information, prompt information is sent to the user, so that the situation that the user cannot generate the steady state node combination information due to misoperation and further cannot realize service recovery is avoided, or the available steady state node combination information is called from other equipment to perform data rollback and the like.
In an exemplary embodiment, the steady-state node combination information includes a steady-state node identification combination, and determining the steady-state node combination information according to the information of the node combination to be confirmed includes:
and combining the identification information of each service node in the node combination to be confirmed to generate a steady-state node identification combination.
The present exemplary embodiment may characterize the steady-state node combination information by using a form of steady-state node identification combination, and when determining the steady-state node combination information according to the information of the node combination to be confirmed, may directly combine the identification information of each service node in the node combination to be confirmed to generate the steady-state node identification combination, for example, may represent mirror image 1 by identification "A1", represent configuration 1 by identification "B1", and then the steady-state node combination information of "mirror image 1+configuration 1" may represent steady-state node identification combination "a1+b1". In particular, the identification information may refer to ID information of the service node.
In an exemplary embodiment, the step S120 may include:
and responding to the rollback confirmation operation, and performing data rollback on the service nodes in the target service according to the steady-state node combination information.
In order to ensure the accuracy of data rollback and avoid abnormal rollback of service, the present exemplary embodiment may send a confirmation prompt window for confirming whether to perform data rollback to the user after determining the steady state node combination information, or may provide an option for confirming whether to rollback in the display interface, when the user inputs the rollback confirmation operation for the current service, the user may perform data rollback on the service node in the target service according to the steady state node combination information, for example, the rollback interface may include a "fast rollback" option, and when the operator performs rollback confirmation operation such as a single click or a double click on the option, the operator may consider that the current confirmation performs the data rollback operation.
In an exemplary embodiment, the service fault handling apparatus may further include:
a visual service management interface is displayed on the display interface to manage one or more services through the visual service management interface.
The display interface may be a display device of a terminal for performing data rollback, such as a display panel connected to a server, etc., and the present exemplary embodiment may manage one or more services through a visual service management interface from which an operator may select a target service and perform a data rollback operation thereon.
The visual service management interface can comprise a service list, the service list can sort the update histories of all services according to time sequence, operation and maintenance personnel can perform operation of rapidly recovering fault service on the interface, and meanwhile, change conditions of all service nodes in any time period before and after the fault occurs can be rapidly checked. The dependency relationship of each service node can be clicked and checked in the details of each service node, and based on the content in the visual service management interface, the operation and maintenance personnel can roll all relevant services back to a stable running state quickly as required, so that fault repair can be completed at the highest speed.
FIG. 3 is a schematic diagram of a portion of a visual service management interface, specifically including an operation interface of a target service when performing data rollback, an operator may select which data rollback service is currently performed according to an option in an indication box 310, for example, a default full-volume rollback may be set, such as a default rollback based on steady-state service node combination information; the fast rollback according to the last generated steady-state service node combination information can be performed; and the steady-state service node combination information can be selected in a self-defined mode according to actual needs to perform full rollback on the target service. FIG. 4 is a partial schematic diagram of service fault recovery in a visual service management interface, where the partial schematic diagram may include detailed information of a flow state, a start time, an end time, a current stage, a current operation and a plurality of indicators of the state, grouping, description and operation, and corresponding indicator values of the data rollback. In addition, in the visual service management interface, the topology map of the service dependency relationship may be displayed, as shown in fig. 5, and service information, call times, and the like of the current service that is called in the last 14 days may be displayed.
Fig. 6 shows another service fault recovery method in the present exemplary embodiment, which may specifically include:
step S610, responding to the change of at least one service node in the target service, and combining the current service nodes in the target service after the change to generate a node combination to be confirmed;
step S620, determining whether the target service operates for a preset time period in a node combination to be confirmed, wherein the target service has no abnormal condition;
if the target service runs for a preset time period with the node combination to be confirmed, the abnormal condition of the target service occurs, and step S630 is executed to obtain steady-state node combination information of the target service with the latest generation time;
step S640, according to the steady-state node combination information, carrying out data rollback on the service node in the target service;
if the target service runs for a preset time period with the node combination to be confirmed, and no abnormal condition occurs in the target service, executing step S650, and generating steady-state node combination information according to the information of the node combination to be confirmed;
step S660, judging whether a discard operation of the steady-state node combination information is received;
if a discard operation is received for the steady-state node combination information, executing step S670, and canceling generation of the steady-state node combination information;
if no discard operation is received for the steady-state node combination information, step S680 is executed to record and update the steady-state node combination information.
It should be noted that, the above processes may be performed in the visual service management interface.
The exemplary embodiment of the disclosure also provides a service fault handling device. Referring to fig. 7, the apparatus 700 may include a combination information obtaining module 710 for obtaining steady-state node combination information of a target service in response to a failure of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service; and the data rollback module 720 is configured to rollback data for the service node in the target service according to the steady node combination information.
In an exemplary embodiment, the service fault handling apparatus further includes: the node combination to be confirmed generating unit is used for responding to the change of at least one service node in the target service before acquiring the steady-state node combination information of the target service, and combining the current service nodes in the target service after the change so as to generate the node combination to be confirmed; and the steady-state node combination information generating unit is used for generating steady-state node combination information according to the information of the node combination to be confirmed when the node combination to be confirmed is confirmed to be stable.
In an exemplary embodiment, the combination information obtaining module is configured to obtain steady-state node combination information of the target service with the latest generation time.
In an exemplary embodiment, the steady-state node combination information generating unit includes: and the service operation judging subunit is used for determining that the node combination to be confirmed is stable when the target service operates for a preset time period with the node combination to be confirmed and the target service has no abnormal condition.
In an exemplary embodiment, the service fault handling apparatus further includes: and the discard operation unit is used for canceling the generation of the steady-state node combination information in response to the discard operation of the steady-state node combination information after the steady-state node combination information is generated according to the information of the node combination to be confirmed.
In an exemplary embodiment, the steady state node combination information includes a steady state node identification combination, and the steady state node combination information generating unit includes: and the identification combination subunit is used for combining the identification information of each service node in the node combination to be confirmed to generate a steady-state node identification combination.
In an exemplary embodiment, a data rollback module includes: and the confirming rollback unit is used for responding to rollback confirmation operation and carrying out data rollback on the service nodes in the target service according to the steady-state node combination information.
The specific details of each part in the above apparatus are already described in the method part embodiments, and the details not disclosed can refer to the embodiment content of the method part, so that the details are not repeated.
Exemplary embodiments of the present disclosure also provide a computer readable storage medium, which may be implemented in the form of a program product comprising program code for causing an electronic device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the above section of the "exemplary method" when the program product is run on the electronic device. In an alternative embodiment, the program product may be implemented as a portable compact disc read only memory (CD-ROM) and comprises program code and may run on an electronic device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Exemplary embodiments of the present disclosure also provide an electronic device. The electronic device may include a processor and a memory. The memory stores executable instructions of the processor, such as program code. The processor performs the method of the present exemplary embodiment by executing the executable instructions. The electronic device may further comprise a display for displaying the graphical user interface.
With reference now to FIG. 8, an electronic device is illustrated in the form of a general purpose computing device. It should be understood that the electronic device 800 illustrated in fig. 8 is merely an example and should not be taken as limiting the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 8, an electronic device 800 may include: processor 810, memory 820, bus 830, I/O (input/output) interface 840, network adapter 850, display 860.
The memory 820 may include volatile memory such as RAM 821, cache unit 822, and nonvolatile memory such as ROM 823. Memory 820 may also include one or more program modules 824, such program modules 824 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. For example, program modules 824 may include modules in the apparatus described above.
Bus 830 is used to enable connections between the different components of electronic device 800 and may include a data bus, an address bus, and a control bus.
The electronic device 800 may communicate with one or more external devices 900 (e.g., keyboard, mouse, external controller, etc.) via the I/O interface 840.
The electronic device 800 may communicate with one or more networks through the network adapter 850, e.g., the network adapter 850 may provide a mobile communication solution such as 3G/4G/5G, or a wireless communication solution such as wireless local area network, bluetooth, near field communication, etc. Network adapter 850 may communicate with other modules of electronic device 800 via bus 830.
The electronic device 800 may display a graphical user interface, such as displaying a game editing scene or the like, via the display 860.
Although not shown in fig. 8, other hardware and/or software modules may also be provided in electronic device 800, including, but not limited to: displays, microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with exemplary embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system. Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A service fault handling method, comprising:
responding to the failure of a target service, and acquiring steady-state node combination information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service;
and according to the steady-state node combination information, carrying out data rollback on the service node in the target service.
2. The method of claim 1, wherein prior to obtaining steady state node combination information for the target service, the method further comprises:
responding to the change of at least one service node in the target service, and combining the current service node in the target service after the change to generate a node combination to be confirmed;
and when the node combination to be confirmed is determined to be stable, generating steady-state node combination information according to the information of the node combination to be confirmed.
3. The method of claim 2, wherein the obtaining steady state node combination information for the target service comprises:
and acquiring steady-state node combination information of the target service with the latest generation time.
4. The method of claim 2, wherein the determining that the node combination to be validated is stable comprises:
and when the target service runs for a preset time period with the node combination to be confirmed and the abnormal condition of the target service does not occur, determining that the node combination to be confirmed is stable.
5. The method of claim 2, wherein after generating steady state node combination information from the information of the node combinations to be validated, the method further comprises:
and canceling the generation of the steady-state node combination information in response to the discard operation of the steady-state node combination information.
6. The method of claim 2, wherein the steady state node combination information comprises a steady state node identification combination, and wherein the determining steady state node combination information from the information of the node combination to be confirmed comprises:
and combining the identification information of each service node in the node combination to be confirmed to generate the steady-state node identification combination.
7. The method of claim 1, wherein said rolling back data for the service node in the target service based on the steady state node combination information comprises:
and responding to rollback confirmation operation, and performing data rollback on the service nodes in the target service according to the steady-state node combination information.
8. A service failure handling apparatus, comprising:
the combined information acquisition module is used for responding to the failure of the target service and acquiring the steady-state node combined information of the target service; the target service comprises a plurality of service nodes, and the steady-state node combination information comprises information of the service nodes in a steady operation state of the target service;
and the data rollback module is used for rolling back the data of the service node in the target service according to the steady-state node combination information.
9. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the method of any of claims 1-6 via execution of the executable instructions.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311073007.1A CN116996365A (en) | 2023-08-23 | 2023-08-23 | Service fault processing method, service fault processing device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311073007.1A CN116996365A (en) | 2023-08-23 | 2023-08-23 | Service fault processing method, service fault processing device, electronic equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116996365A true CN116996365A (en) | 2023-11-03 |
Family
ID=88521401
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311073007.1A Pending CN116996365A (en) | 2023-08-23 | 2023-08-23 | Service fault processing method, service fault processing device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116996365A (en) |
-
2023
- 2023-08-23 CN CN202311073007.1A patent/CN116996365A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6684180B2 (en) | Apparatus, system and method for reporting field replaceable unit replacement | |
| CN103314359A (en) | System and method for updating firmware | |
| US20090282141A1 (en) | Server managing apparatus and server managing method | |
| US7062679B2 (en) | Computer recovery supporting apparatus and method, and computer recovery supporting program | |
| US20140201566A1 (en) | Automatic computer storage medium diagnostics | |
| CN111694684A (en) | Abnormal construction method and device of storage equipment, electronic equipment and storage medium | |
| CN116996365A (en) | Service fault processing method, service fault processing device, electronic equipment and medium | |
| JP2019020798A (en) | Information processing device and program | |
| US20160203040A1 (en) | Error display module | |
| CN111124095B (en) | Power supply running state detection method and related device during upgrading of power supply firmware | |
| CN113127029A (en) | Firmware updating method and device, electronic equipment and storage medium | |
| CN113128730A (en) | Ticket information interaction method, server, equipment and medium | |
| CN111542048A (en) | Method and device for restarting acquisition function of code detection equipment, server and storage medium | |
| CN114466026B (en) | Update method and device of application program interface, storage medium and computing device | |
| CN114655140B (en) | Vehicle starting control method and related device | |
| CN111951489B (en) | Intelligent cabinet batch flashing method, device, equipment and storage medium | |
| JP5422490B2 (en) | Computer system and I / O fault card identification method | |
| CN115292123A (en) | System exception handling method and device, storage medium and electronic equipment | |
| CN108763013B (en) | Fault processing method, device, equipment and computer storage medium | |
| EP2391944A1 (en) | System care of computing devices | |
| CN114466026A (en) | Application program interface updating method and device, storage medium and computing equipment | |
| EP0471638A2 (en) | Problem prevention on a computer system in a service network of computer systems | |
| CN117931239A (en) | Processing method and electronic equipment | |
| CN116069564A (en) | Container monitoring method, device, equipment and medium | |
| CN114036420A (en) | Page rollback method, device, equipment and storage medium |
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 |