CN110928714A - A service exception processing method, device and computing device - Google Patents
- ️Fri Mar 27 2020
CN110928714A - A service exception processing method, device and computing device - Google Patents
A service exception processing method, device and computing device Download PDFInfo
-
Publication number
- CN110928714A CN110928714A CN201811120304.6A CN201811120304A CN110928714A CN 110928714 A CN110928714 A CN 110928714A CN 201811120304 A CN201811120304 A CN 201811120304A CN 110928714 A CN110928714 A CN 110928714A Authority
- CN
- China Prior art keywords
- virtual machine
- abnormal event
- execution time
- response
- associated virtual Prior art date
- 2018-09-19 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 2
- 230000002159 abnormal effect Effects 0.000 claims abstract description 130
- 230000010485 coping Effects 0.000 claims abstract description 52
- 230000004044 response Effects 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims abstract description 16
- 238000000034 method Methods 0.000 claims description 61
- 230000036541 health Effects 0.000 claims description 15
- 238000012423 maintenance Methods 0.000 claims description 11
- 230000003862 health status Effects 0.000 claims description 9
- 230000005856 abnormality Effects 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 7
- 230000008439 repair process Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000007723 transport mechanism Effects 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0712—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a virtual computing platform, e.g. logically partitioned systems
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
本发明公开了一种服务异常处理方法,包括:向终端设备发送异常事件信息,异常事件信息包括受异常事件影响的关联虚拟机、针对异常事件的应对操作以及应对操作的计划执行时间;在计划执行时间之前,接收终端设备对于异常事件的响应;当响应为设置应对操作的替代执行时间时,在替代执行时间对关联虚拟机执行所述应对操作。本发明一并公开了相应的服务异常处理装置以及计算设备。
The invention discloses a service abnormality processing method, comprising: sending abnormal event information to a terminal device, the abnormal event information includes an associated virtual machine affected by the abnormal event, a coping operation for the abnormal event, and a planned execution time of the coping operation; Before the execution time, the response of the terminal device to the abnormal event is received; when the response is to set an alternative execution time for the coping operation, the coping operation is executed on the associated virtual machine at the alternative execution time. The invention also discloses a corresponding service exception processing device and a computing device.
Description
Technical Field
The present invention relates to the field of elastic technologies, and in particular, to a method and an apparatus for processing a service exception, and a computing device.
Background
An Elastic Computing Service (ECS) provides a basic cloud computing Service for users, and users may deploy various Service systems by creating instances on a cloud server. An example is a virtual machine, which includes basic computing components such as a CPU, memory, operating system, network, disk, etc., and can be used to perform computing tasks set by a user.
The abnormal event refers to a planned or unexpected event which affects the running state of the virtual machine, such as an event of restarting, stopping or releasing an ECS instance and the like which occurs due to update maintenance, illegal operation, system failure, software and hardware failure, imminent prepayment expiration or account number defaulting and the like.
In the existing scheme, when an unexpected abnormal event occurs, a user can only perceive the abnormal operation of the virtual machine, and cannot know the reason of the abnormal operation of the virtual machine. The user usually needs to find out the abnormal reason by contacting customer service, contacting customer manager, submitting work order and the like, which is troublesome and laborious, and it is difficult to repair the abnormal virtual machine in a targeted manner according to the abnormal reason.
Therefore, there is a need for a more efficient and transparent method of handling service exceptions that is interactive for the user.
Disclosure of Invention
To this end, the present invention provides a service exception handling method, apparatus and computing device in an attempt to solve or at least alleviate the problems presented above.
According to an aspect of the present invention, there is provided a service exception handling method, including: sending abnormal event information to a terminal device, wherein the abnormal event information comprises an associated virtual machine influenced by the abnormal event, a handling operation aiming at the abnormal event and a scheduled execution time of the handling operation; receiving a response of the terminal device to the abnormal event before the scheduled execution time; when the response is to set an alternative execution time of the coping operation, executing the coping operation on the associated virtual machine at the alternative execution time.
According to an aspect of the present invention, there is provided a service exception handling method, including: receiving abnormal event information sent by a server, wherein the abnormal event information comprises an associated virtual machine influenced by the abnormal event, a handling operation aiming at the abnormal event and a scheduled execution time of the handling operation; and returning a response to the abnormal event to a server before the scheduled execution time, and when the response is the setting of the alternative execution time of the coping operation, instructing the server to execute the coping operation on the associated virtual machine at the alternative execution time.
According to an aspect of the present invention, there is provided a service exception handling apparatus including: the notification module is suitable for sending abnormal event information to the terminal equipment, wherein the abnormal event information comprises an associated virtual machine influenced by the abnormal event, a handling operation aiming at the abnormal event and a scheduled execution time of the handling operation; the receiving module is suitable for receiving the response of the terminal equipment to the abnormal event; and the execution module is suitable for executing the coping operation on the associated virtual machine at the alternative execution time when the response is to set the alternative execution time of the coping operation.
According to an aspect of the present invention, there is provided a service exception handling apparatus including: the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is suitable for receiving abnormal event information sent by a server, and the abnormal event information comprises an associated virtual machine influenced by the abnormal event, a handling operation aiming at the abnormal event and a scheduled execution time of the handling operation; and the feedback module is suitable for returning a response to the abnormal event to the server, and when the response is to set the alternative execution time of the coping operation, the feedback module instructs the server to execute the coping operation on the associated virtual machine at the alternative execution time.
According to an aspect of the invention, there is provided a computing device comprising: at least one processor; and a memory storing program instructions, wherein the program instructions are configured to be executed by the at least one processor, the program instructions comprising instructions for performing the service exception handling method as described above.
According to yet another aspect of the present invention, there is provided a readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the service exception handling method as described above.
According to the technical scheme of the invention, aiming at the planned abnormal event, the server sends the abnormal event information to the user (namely the terminal equipment) to inform the user of the related virtual machine influenced by the abnormal event, the handling operation aiming at the abnormal event and the planned execution time of the handling operation. The user may respond to the exception event prior to the scheduled execution time based on the notification. In response to the user setting the alternative execution time for the coping operation, the server executes the coping operation at the alternative execution time set by the user. In this way, the user can interact with the server with respect to the execution time and execution mode of the coping operation, instead of being only able to passively accept and wait for the coping operation of the abnormal event to be executed. The user can reserve proper time (namely, substitute execution time) to execute coping operation, reserve sufficient time to perform data backup, and reduce the influence of abnormal events on the existing business of the user.
Further, for a planned abnormal event, the server may also recommend a recommended operation for the abnormal event to the user. Before the user plans the execution time, the user can send an instruction to the server to immediately execute a certain item or a certain plurality of recommended operations, and the server executes the recommended operations instructed by the user. Therefore, the user can immediately take appropriate measures for the abnormal event without waiting for the later scheduled execution time to execute the corresponding operation, so that the abnormal event can be responded in time, and the influence of the abnormal event on the existing service is reduced.
Furthermore, the health state information of the virtual machine is determined according to the running state information of the virtual machine and the physical machine where the virtual machine is located, and the health state information is pushed to the user, so that the user can sense the real-time state of the virtual machine, and when the virtual machine is abnormal, the reason for generating the abnormality is conveniently located.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which are indicative of various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description read in conjunction with the accompanying drawings. Throughout this disclosure, like reference numerals generally refer to like parts or elements.
FIG. 1 shows a schematic diagram of a service exception handling system 100 according to one embodiment of the present invention;
FIG. 2 illustrates a flow diagram of a service
exception handling method200 according to one embodiment of the invention;
FIG. 3 illustrates a schematic diagram of state switching of an exception event, according to one embodiment of the present invention;
FIG. 4 shows a schematic diagram of a service exception handling process according to one embodiment of the invention;
FIG. 5 illustrates a flow diagram of a service
exception handling method500 according to one embodiment of the invention;
FIG. 6 shows a schematic diagram of a computing device 600, according to one embodiment of the invention;
FIG. 7 shows a schematic diagram of a service exception handling
apparatus700 according to one embodiment of the present invention;
FIG. 8 shows a schematic diagram of a service exception handling
apparatus800 according to one embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
FIG. 1 shows a schematic diagram of a service exception handling system 100 according to one embodiment of the present invention. As shown in FIG. 1, the system 100 for processing service exception includes physical machines 110(110-1 to 110-3), a
server120 and terminal devices 130(130-1 to 130-3).
The
physical machine110 may be, for example, any configuration of physical servers for providing Elastic Computing Services (ECS), and any number of virtual machines (virtualmachines) may be deployed on the
physical machine110. A virtual machine refers to a computer system, simulated by software, having complete hardware system functionality, running in a completely isolated environment, created for user-based requests, for performing user's computing tasks. In some embodiments, a virtual machine may also be referred to as an instance. For example, as shown in fig. 1, a virtual machine 1 and a virtual machine 2 are deployed on a physical machine 110-1; the physical machine 110-2 is provided with a virtual machine 3; the physical machine 110-3 is deployed with virtual machines 4-6.
Generally, the plurality of
physical machines110 may form an elastic service cluster, and a scheduling server, a load balancing server, and the like (note that the scheduling server and the load balancing server are not shown in fig. 1) are preferably further provided in the cluster for managing and scheduling the physical machines in the cluster.
The
terminal device130 is a device on the user side, and may be a personal computer such as a desktop computer and a notebook computer, or a mobile device such as a mobile phone, a tablet computer, a multimedia device, and a smart wearable device, but is not limited thereto. The
server120 may be one of a cluster of resilient services that may communicate with a dispatch server of the cluster. In one embodiment, the
server120 may also be the dispatch server itself of the elastic service cluster.
A user initiates a request for creating a virtual machine to the cluster through the
server120, where the request includes relevant configuration parameters of the virtual machine selected by the user, such as CPU core number, memory capacity, disk capacity, operating system, and the like.
Server120 receives the request and forwards the request to the dispatch server of the cluster. The scheduling server refers to the remaining resource amount, the remaining resource rate, the network communication status and other factors of each physical machine and allocates the request to the appropriate physical machine. The appropriate physical machine then allocates the resources indicated by the configuration parameters set by the user based on the request, and creates a virtual machine based on the allocated resources. The virtual machine may then perform the computing task instructed by the user.
After the virtual machines are created on the
physical machines110, the
server120 may provide a virtual machine monitoring service to the user so that the user may monitor the health status information of each virtual machine that he or she creates on the
terminal device130. Specifically, the user may create a virtual machine through a specific Application (APP) installed on the
terminal device130 and view health status information of each virtual machine created by the user (accordingly, the
server120 is an application server corresponding to the specific application); it is also possible to create a virtual machine and view health status information of each virtual machine created by the virtual machine by accessing a specific website through a browser on the terminal device 130 (accordingly, the
server120 is a Web server corresponding to the website). The
server120 may, for example, directly obtain the health information of each physical machine and the virtual machines running on each physical machine periodically (for example, obtain the health information once every 1 minute) or obtain the health information of each virtual machine running on each physical machine periodically from a scheduling server of the cluster, determine the health information of each virtual machine according to the running information of the physical machine and the virtual machines on the physical machine, store the health information of the virtual machine in association with the user identifier corresponding to the virtual machine, and push the health information of the virtual machine corresponding to the user when the user accesses the corresponding application or website through the
terminal device130.
In one embodiment, the health status information of the virtual machine is determined by the running status information of the virtual machine and the running status information of the physical machine where the virtual machine is located, and preferably, the user may view the running status information of the virtual machine and the physical machine where the virtual machine is located together on the
terminal device130. The operation state information of the virtual machine may include, for example, a plurality of contents such as a virtual CPU usage rate and a network traffic, and may be specifically referred to in table 1 below. Those skilled in the art will understand that only a part of the items that may be included in the running state information are shown in table 1, and in practice, the running state information of the virtual machine may include all the items in table 1, only a part of the items in table 1 may be selected, and other items not listed in table 1 may also be included. The invention does not limit the specific information items included in the running state information of the virtual machine.
TABLE 1 State information for virtual machines
Running status information items | Item interpretation |
vCPU (virtual CPU) | Example vCPU usage ratio, unit: is based on |
Flow rate in the direction of internal network entry | Example is in the received data traffic of the intranet, unit: kbits |
Inner net outlet flow | Example in the case of the sent data traffic of the intranet, the unit: kbits |
Bandwidth of internal network | Example intranet bandwidth, network traffic in unit time, unit: kbits/s |
Public network access direction traffic | Example received public network data traffic, unit: kbits |
Public network outgoing direction flow | Example sent public network data traffic, unit: kbits |
Bandwidth of public network | Example public network bandwidth, network traffic per unit time, unit: kbits/s |
System disk read operation | Total number of bytes read per second for system disk, unit: order/s |
System disk write operation | Total number of bytes written per second for system disk, unit: order/s |
System disk read bandwidth | Number of reads per second for system disk, unit: byte/s |
System disk write bandwidth | Number of writes per second for system disk, unit: byte/s |
The running state information of the physical machine includes state information of hardware and software on the physical machine, the hardware state information includes, for example, a working state of hardware such as a CPU, a memory bank, a disk, a network card, and the like, and the software state information includes a running state of an operating system of the physical machine and virtualization platform software (e.g., VMware, VirtualBox, virtualpc, and the like).
The health state of the virtual machine is determined by the running state of the virtual machine and the running state of the physical machine in which the virtual machine is located. In one embodiment, a person skilled in the art may preset a corresponding relationship between the health state and the operating states of the virtual machine and the physical machine, and then may determine the health state of the virtual machine according to the operating states of the virtual machine and the physical machine. For example, it may be set that the health state of the virtual machine is "healthy" when all the running state information of the virtual machine and the physical machine is normal, the health state of the virtual machine is "early warning" when some running state information of the virtual machine and the physical machine is abnormal, and the health state of the virtual machine is "failure" when many running state information of the virtual machine and the physical machine is abnormal or a certain part is seriously abnormal, and so on. Of course, besides the above methods, those skilled in the art may also use other methods to determine the health status information of the virtual machine according to the running status information of the virtual machine and the physical machine, and the specific determination method of the health status information of the virtual machine is not limited in the present invention.
In one embodiment, some planned exception events that affect the normal operation of the virtual machine may be generated based on the operating state of the physical machine. For example, when a backup disk on a physical machine fails, the failed backup disk does not immediately affect normal operations of the physical machine and a virtual machine on the physical machine, but there is a risk of affecting operations of the physical machine and the virtual machine. In order to avoid adverse effects on the physical machine and the virtual machine, the backup disk needs to be replaced at a future time, so that the physical machine is restored to a state that the backup disk is completely intact. When a backup disk is replaced, the physical machine may be shut down and, accordingly, the virtual machines on the physical machine may be halted. Therefore, it can be understood that when the backup disk of the physical machine fails, the disk of the physical machine is in an early warning state, the early warning state corresponds to a planned abnormal event, and the abnormal event affects the operation of the virtual machine on the physical machine. Corresponding countermeasures need to be taken at a future time for the abnormal event. Of course, besides the above-mentioned physical machine operation state warning, other factors may also generate planned abnormal events, such as system periodic maintenance, financial factors (e.g., the user's prepayment for the flexible computing service is about to expire, the user account arrears), and so on. Unexpected abnormal events may result, for example, from sudden failures of physical machines or human violations.
In order to enable a user to interactively, more efficiently and transparently take countermeasures when a planned abnormal event occurs, the invention provides a service exception handling method, which is described in detail below.
FIG. 2 shows a flow diagram of a service
exception handling method200 according to one embodiment of the invention. The
method200 is performed on a server, such as the
aforementioned server120. As shown in fig. 2, the
method200 begins at step S210.
In step S210, abnormal event information including the associated virtual machine affected by the abnormal event, the coping operation for the abnormal event, and the scheduled execution time of the coping operation is transmitted to the terminal device. The coping operation may be, for example, stopping the associated virtual machine or migrating the associated virtual machine.
For example, the abnormal event may be a disk occurrence warning of a certain physical machine, accordingly, the associated virtual machine affected by the abnormal event is a virtual machine on the physical machine corresponding to the user identifier of the terminal device, the handling operation for the abnormal event may be to replace a disk on the physical machine, stop or migrate the associated virtual machine, and the scheduled execution time may be a certain time in the future, for example, may be set to be 7 days or 14 days after the current time.
In one embodiment, the exception event information further includes at least one recommended operation for the exception time, and the recommended operation may be, for example and without limitation, backing up data in the associated virtual machine, restarting the associated virtual machine, stopping the associated virtual machine, migrating the associated virtual machine, and the like.
In step S220, before the execution time is planned, a response of the terminal device to the abnormal event is received.
There are various responses described in step S220. In one embodiment, the response of the terminal device to the abnormal event may be setting an alternative execution time for the coping operation, and the alternative execution time may be any time other than the scheduled execution time that has not yet come. When a user needs to backup important data related to a relevant virtual machine due to business consistency, the scheduled execution time set by the system may not be suitable for a terminal device user. In this case, the user may return a response to the server, reserve an appropriate time (i.e., an alternative execution time) to perform the handling operation, reserve sufficient time to perform data backup, and reduce the influence of the abnormal event on its existing service.
In another embodiment, the response of the terminal device to the exception event may be to send an indication that at least one of the recommended operations is to be performed immediately. When a user has a backup of data for an associated virtual machine that requires maintaining computing performance, the user may prefer that the associated virtual machine be able to resume production as soon as possible. In this case, the user can immediately take appropriate measures against the abnormal event without waiting for the scheduled execution time to execute the coping operation again.
Subsequently, in step S230, when the response is to set the substitute execution time of the coping operation, the coping operation is performed on the associated virtual machine at the substitute execution time.
And when the response is to send an instruction for immediately executing at least one item of the recommended operation, executing the instructed recommended operation on the associated virtual machine, and not executing the preset coping operation any more.
FIG. 3 illustrates a schematic diagram of state switching of an exception event according to one embodiment of the present invention. As shown in fig. 3, when a planned abnormal event occurs due to a physical machine failure, system maintenance, financial factors, or the like, the server issues the abnormal event, and pushes the abnormal event information to the corresponding terminal device, so that the user at the terminal device knows the abnormal event. The abnormal event information includes the associated virtual machine of the user affected by the abnormal event, a recommended operation for the abnormal event, a coping operation, and a scheduled execution time of the coping operation. The user may respond to the exception event before the scheduled execution time.
If the user performs the recommended operation before the scheduled execution time, the exception is avoided and the exception is ended. The server will not perform the coping operation at the originally scheduled execution time.
If the user modifies the execution time before the scheduled execution time, i.e., the scheduled execution time is modified to the alternative execution time, the server will perform the corresponding operation at the alternative execution time set by the user. And after the coping operation is successfully executed, ending the abnormal event.
If the user does not respond before the scheduled execution time, the server performs a coping operation at the preset scheduled execution time. And after the coping operation is successfully executed, ending the abnormal event.
As can be seen from fig. 3, the user may perform the recommended operation before the scheduled execution time, set the alternative execution time for the handling operation, and not respond any more, which may result in the end of the abnormal event. It will be appreciated by those skilled in the art that there are other situations besides the three above which can cause the exception to end, for example, the server cancels the exception.
FIG. 4 shows a schematic diagram of a service exception handling process according to one embodiment of the invention. As shown in fig. 4, the
physical machine110 reports a disk or component alert to the
server120. Specifically, the
physical machine110 may be deployed with IDC (internet data Center) operation and maintenance system software and ECS operation and maintenance system software, where the IDC operation and maintenance system is configured to collect (for example, once per minute) operation state information about storage and network on the
physical machine110 according to a predetermined frequency, and report the operation state information to the ECS operation and maintenance system. The ECS operation and maintenance system determines that an abnormality occurs on the
physical machine110 according to the operation state information reported by the IDC operation and maintenance system, for example, determines that a disk or other component on the
physical machine110 gives an alarm. The exception is then reported to the
server120.
The
server120 generates an abnormal event based on the alarm information reported by the
physical machine110, and sends the abnormal event information to the relevant
terminal device130. The abnormal event information includes the associated virtual machine affected by the abnormal event, a recommended operation for the abnormal event, a coping operation, and a scheduled execution time of the coping operation. The coping operation is, for example, stopping the virtual machine on the
physical machine110 and repairing or replacing an abnormal disk or component on the
physical machine110, and the recommended operation may be, for example, migrating the virtual machine.
The
terminal device130 may respond to the exception event before the scheduled execution time. As shown in fig. 4, the response includes three types: 1) no operation is performed; 2) executing recommendation operation, and migrating the virtual machine on the
physical machine110 to other physical machines for running; 3) an alternative execution time is set.
The
server120 receives a response of the
terminal device130 to the abnormal event and issues an instruction to the
physical machine110 based on the response. When the user responds as not to perform any operations, the
server120 instructs the
physical machine110 to shutdown the virtual machine on it at the scheduled execution time. When the user performs the recommended operation (for example, migrating the virtual machine) by himself, the abnormal event is ended, and the
server120 does not perform the subsequent operation any more. When the user's response is to set the alternate execution time, the
server120 instructs the
physical machine110 to shutdown the virtual machine thereon at the alternate execution time set by the user.
After the virtual machine on the
physical machine110 is stopped, the worker replaces or repairs the abnormal disk or component on the
physical machine110. After the repair is completed, the
physical machine110 sends a notification of the repair completion to the
server120, and the
server120 further sends the notification of the repair completion to the
terminal device130 to notify the user that the repair of the
physical machine110 is completed, so that the virtual machine can be restarted. Subsequently, the user can check the running state of the virtual machine on the
terminal device130, and resume the calculation task as appropriate.
FIG. 5 shows a flow diagram of a service
exception handling method500 according to one embodiment of the invention.
Method500 is performed on a terminal device, such as
terminal device130 described above. As shown in fig. 5, the
method500 begins at step S510.
In step S510, the abnormal event information sent by the server is received, and the abnormal event information includes the associated virtual machine affected by the abnormal event, the handling operation for the abnormal event, and the scheduled execution time of the handling operation. The coping operation may be, for example, stopping the associated virtual machine or migrating the associated virtual machine.
For example, the abnormal event may be a disk occurrence warning of a certain physical machine, accordingly, the associated virtual machine affected by the abnormal event is a virtual machine on the physical machine corresponding to the user identifier of the terminal device, the handling operation for the abnormal event may be to replace a disk on the physical machine, stop or migrate the associated virtual machine, and the scheduled execution time may be a certain time in the future, for example, may be set to be 7 days or 14 days after the current time.
In one embodiment, the exception event information further includes at least one recommended operation for the exception time, and the recommended operation may be, for example and without limitation, backing up data in the associated virtual machine, restarting the associated virtual machine, stopping the associated virtual machine, migrating the associated virtual machine, and the like.
Subsequently, in step S520, a response to the abnormal event is returned to the server before the execution time is planned, and when the response is to set an alternative execution time for the coping operation, the server is instructed to execute the coping operation on the associated virtual machine at the alternative execution time. In another embodiment, the response may also be to send an indication that at least one of the recommended operations is to be performed immediately, and accordingly, the server performs the indicated recommended operation on the associated virtual machine without performing the preset coping operation any longer.
FIG. 6 shows a block diagram of a computing device 600, according to one embodiment of the invention. The computing device 600 may be implemented, for example, as the aforementioned
physical machine110,
server120, and
terminal device130. Of course, the computing device 600 is only an example, in an actual configuration, the
physical machine110, the
server120, and the
terminal device130 may delete some modules in the computing device 600 (for example, remove the
audio processing unit660, etc.) or add some modules that are not in the computing device 600 according to actual needs, and the present invention does not limit the specific configuration of the
physical machine110, the
server120, and the
terminal device130.
As shown in fig. 6, in a basic configuration 602, computing device 600 typically includes a system memory 606 and one or more processors 604. A memory bus 608 may be used for communicating between the processor 604 and the system memory 206.
Depending on the desired configuration, the processor 204 may be any type of processing, including but not limited to: a microprocessor (μ P), a microcontroller (μ C), a Digital Signal Processor (DSP), or any combination thereof. Processor 604 may include one or more levels of cache, such as a level one
cache610 and a level two
cache612, a
processor core614, and registers 616.
Example processor cores614 may include Arithmetic Logic Units (ALUs), Floating Point Units (FPUs), digital signal processing cores (DSP cores), or any combination thereof. The example memory controller 618 may be used with the processor 604, or in some implementations the memory controller 618 may be an internal part of the processor 604.
Depending on the desired configuration, system memory 606 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 606 may include an operating system 620, one or more applications 622, and
program data624. The application 622 is actually a plurality of program instructions that direct the processor 604 to perform corresponding operations. In some implementations, the application 622 can be arranged to cause the processor 604 to operate with
program data624 on an operating system.
Computing device 600 may also include an interface bus 640 that facilitates communication from various interface devices (e.g., output devices 642, peripheral interfaces 644, and communication devices 646) to the basic configuration 602 via the bus/
interface controller630. The example output device 642 includes a graphics processing unit 648 and an audio processing unit 650. They may be configured to facilitate communication with various external devices, such as a display or speakers, via one or more a/V ports 252. Example peripheral interfaces 644 can include a
serial interface controller654 and a
parallel interface controller656, which can be configured to facilitate communications with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/
O ports658. An example communication device 646 can include a
network controller660, which can be arranged to facilitate communications with one or more
other computing devices662 over a network communication link via one or
more communication ports664.
A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, Radio Frequency (RF), microwave, Infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.
In the computing device 600 according to the invention, the application 622 may for example comprise a service
exception handling apparatus700 or 800, both
apparatuses700 or 800 comprising a plurality of program instructions, but the specific program instructions comprised by the two are different. Service
exception handling apparatus700 may direct processor 704 to perform service
exception handling method200 of the present invention, thereby enabling computing device 600 to be implemented as
server120 of the present invention. Service
exception handling apparatus800 may instruct processor 704 to perform service
exception handling method500 of the present invention, thereby enabling computing device 600 to be implemented as
terminal device130 of the present invention.
FIG. 7 shows a schematic diagram of a service
exception handling apparatus700 according to one embodiment of the present invention. The service
exception handling apparatus700 resides in the
server120 and is configured to perform the service
exception handling method200 of the present invention. As shown in fig. 7, the service
exception handling apparatus700 includes a
notification module710, a receiving
module720, and an executing
module730.
The
notification module710 is adapted to send abnormal event information to the terminal device, where the abnormal event information includes the associated virtual machine affected by the abnormal event, a handling operation for the abnormal event, and a scheduled execution time of the handling operation. The
notification module710 is specifically configured to execute the method of step S210, and for processing logic and functions of the
notification module710, reference may be made to the related description of step S210, which is not described herein again.
A receiving
module720, adapted to receive a response of the terminal device to the abnormal event. The receiving
module720 is specifically configured to execute the method of step S220, and for processing logic and functions of the receiving
module720, reference may be made to the related description of step S220, which is not described herein again.
The
execution module730 is adapted to execute the coping operation on the associated virtual machine at the alternative execution time when the response is to set the alternative execution time of the coping operation. The executing
module730 is specifically configured to execute the method of step S230, and for the processing logic and function of the executing
module730, reference may be made to the related description of step S230, which is not described herein again.
FIG. 8 shows a schematic diagram of a service
exception handling apparatus800 according to one embodiment of the invention. The service
exception handling apparatus800 resides in the
terminal device130 and is configured to execute the service
exception handling method500 of the present invention. As shown in fig. 8, the service
exception handling apparatus800 includes a receiving
module810 and a
feedback module820.
The receiving
module810 is adapted to receive abnormal event information sent by the server, where the abnormal event information includes an associated virtual machine affected by the abnormal event, a handling operation for the abnormal event, and a scheduled execution time of the handling operation. The receiving
module810 is specifically configured to execute the method of step S510, and for processing logic and functions of the receiving
module810, reference may be made to the related description of step S510, which is not described herein again.
And the
feedback module820 is suitable for returning a response to the abnormal event to the server, and when the response is the setting of the alternative execution time of the coping operation, instructing the server to execute the coping operation on the associated virtual machine at the alternative execution time. The
feedback module820 is specifically configured to execute the method of step S520, and for processing logic and functions of the
feedback module820, reference may be made to the related description of step S520, which is not described herein again.
The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U.S. disks, floppy disks, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein the memory is configured to store program code; the processor is configured to execute the service exception handling method of the present invention according to instructions in the program code stored in the memory.
By way of example, and not limitation, readable media may comprise readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.
In the description provided herein, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with examples of this invention. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
Furthermore, some of the described embodiments are described herein as a method or combination of method elements that can be performed by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purpose of carrying out the invention.
As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The present invention has been disclosed in an illustrative rather than a restrictive sense with respect to the scope of the invention, as defined in the appended claims.
Claims (17)
1.一种服务异常处理方法,包括:1. A service exception handling method, comprising: 向终端设备发送异常事件信息,所述异常事件信息包括受所述异常事件影响的关联虚拟机、针对所述异常事件的应对操作以及所述应对操作的计划执行时间;Sending abnormal event information to the terminal device, the abnormal event information including the associated virtual machine affected by the abnormal event, the response operation for the abnormal event, and the planned execution time of the response operation; 在所述计划执行时间之前,接收终端设备对于所述异常事件的响应;Before the planned execution time, receive the response of the terminal device to the abnormal event; 当所述响应为设置所述应对操作的替代执行时间时,在所述替代执行时间对所述关联虚拟机执行所述应对操作。When the response is to set an alternate execution time for the coping operation, the coping operation is performed on the associated virtual machine at the alternate execution time. 2.如权利要求1所述的方法,其中,所述异常事件信息还包括针对所述异常事件的至少一项推荐操作,所述响应还包括发送立即执行所述推荐操作中的至少一项的指示。2. The method of claim 1, wherein the abnormal event information further comprises at least one recommended operation for the abnormal event, and the response further comprises sending a request to immediately perform at least one of the recommended operations. instruct. 3.如权利要求1所述的方法,其中,所述应对操作包括停止关联虚拟机、迁移关联虚拟机。3. The method of claim 1, wherein the coping operation comprises stopping the associated virtual machine, migrating the associated virtual machine. 4.如权利要求2所述的方法,其中,所述推荐操作包括:备份关联虚拟机中的数据、重启关联虚拟机、停止关联虚拟机、迁移关联虚拟机。4. The method of claim 2, wherein the recommended operation comprises: backing up data in the associated virtual machine, restarting the associated virtual machine, stopping the associated virtual machine, and migrating the associated virtual machine. 5.如权利要求1-4中任一项所述的方法,其中,所述异常事件信息还包括异常事件产生的原因,所述原因包括物理机运行状态预警、系统维护或故障、财务因素。5. The method according to any one of claims 1-4, wherein the abnormal event information further includes the cause of the abnormal event, and the cause includes early warning of the running state of the physical machine, system maintenance or failure, and financial factors. 6.如权利要求1所述的方法,还包括:6. The method of claim 1, further comprising: 获取各虚拟机以及各虚拟机所在的物理机的运行状态信息;Obtain the running status information of each virtual machine and the physical machine where each virtual machine is located; 针对一个虚拟机,根据该虚拟机以及该虚拟机所在的物理机的运行状态信息来确定该虚拟机的健康状态信息;For a virtual machine, determine the health state information of the virtual machine according to the running state information of the virtual machine and the physical machine where the virtual machine is located; 将虚拟机的健康状态信息发送至相应的终端设备。Send the health status information of the virtual machine to the corresponding terminal device. 7.如权利要求6所述的方法,其中,物理机的运行状态信息包括物理机上的磁盘的状态信息,磁盘的预警状态对应于一个异常事件,受所述异常事件影响的关联虚拟机为所述物理机上运行的虚拟机。7. The method according to claim 6, wherein the running state information of the physical machine comprises the state information of the disk on the physical machine, the early warning state of the disk corresponds to an abnormal event, and the associated virtual machine affected by the abnormal event is all the related virtual machines. A virtual machine running on the physical machine described above. 8.一种服务异常处理方法,包括:8. A service exception handling method, comprising: 接收服务器发送的异常事件信息,所述异常事件信息包括受所述异常事件影响的关联虚拟机、针对所述异常事件的应对操作以及所述应对操作的计划执行时间;Receive abnormal event information sent by the server, where the abnormal event information includes associated virtual machines affected by the abnormal event, a response operation for the abnormal event, and a planned execution time of the response operation; 在所述计划执行时间之前,向服务器返回对于所述异常事件的响应,当所述响应为设置所述应对操作的替代执行时间时,指示所述服务器在所述替代执行时间对所述关联虚拟机执行所述应对操作。Before the planned execution time, return a response to the abnormal event to the server, and when the response is to set an alternate execution time for the coping operation, instruct the server to respond to the associated virtual event at the alternate execution time The machine performs the coping operation. 9.如权利要求8所述的方法,其中,所述异常事件信息还包括针对所述异常事件的至少一项推荐操作,所述响应还包括发送立即执行所述推荐操作中的至少一项的指示。9. The method of claim 8, wherein the abnormal event information further comprises at least one recommended operation for the abnormal event, and the response further comprises sending a request to immediately perform at least one of the recommended operations instruct. 10.如权利要求8所述的方法,其中,所述应对操作包括停止关联虚拟机、迁移关联虚拟机。10. The method of claim 8, wherein the coping operation comprises stopping the associated virtual machine, migrating the associated virtual machine. 11.如权利要求9所述的方法,其中,所述推荐操作包括:备份关联虚拟机中的数据、重启关联虚拟机、停止关联虚拟机、迁移关联虚拟机。11. The method of claim 9, wherein the recommended operation comprises: backing up data in the associated virtual machine, restarting the associated virtual machine, stopping the associated virtual machine, and migrating the associated virtual machine. 12.如权利要求8-11中任一项所述的方法,其中,所述异常事件信息还包括异常事件产生的原因,所述原因包括物理机运行状态预警、系统维护或故障、财务因素。12. The method according to any one of claims 8-11, wherein the abnormal event information further includes the cause of the abnormal event, and the cause includes early warning of the running state of the physical machine, system maintenance or failure, and financial factors. 13.如权利要求8所述的方法,还包括:13. The method of claim 8, further comprising: 接收虚拟机的健康状态信息,所述健康状态信息根据所述虚拟机以及所述虚拟机所在的物理机的运行状态信息而确定。Health status information of the virtual machine is received, where the health status information is determined according to the running status information of the virtual machine and the physical machine where the virtual machine is located. 14.一种服务异常处理装置,包括:14. A service exception handling device, comprising: 通知模块,适于向终端设备发送异常事件信息,所述异常事件信息包括受所述异常事件影响的关联虚拟机、针对所述异常事件的应对操作以及所述应对操作的计划执行时间;a notification module, adapted to send abnormal event information to the terminal device, the abnormal event information including the associated virtual machine affected by the abnormal event, the response operation for the abnormal event, and the planned execution time of the response operation; 接收模块,适于接收终端设备对于所述异常事件的响应;a receiving module, adapted to receive the response of the terminal device to the abnormal event; 执行模块,适于在所述响应为设置所述应对操作的替代执行时间时,在所述替代执行时间对所述关联虚拟机执行所述应对操作。An execution module adapted to execute the coping operation on the associated virtual machine at the alternate execution time when the response is to set an alternate execution time for the coping operation. 15.一种服务异常处理装置,包括:15. A service exception processing device, comprising: 接收模块,适于接收服务器发送的异常事件信息,所述异常事件信息包括受所述异常事件影响的关联虚拟机、针对所述异常事件的应对操作以及所述应对操作的计划执行时间;a receiving module, adapted to receive abnormal event information sent by the server, where the abnormal event information includes associated virtual machines affected by the abnormal event, a response operation for the abnormal event, and a planned execution time of the response operation; 反馈模块,适于向服务器返回对于所述异常事件的响应,当所述响应为设置所述应对操作的替代执行时间时,指示所述服务器在所述替代执行时间对所述关联虚拟机执行所述应对操作。The feedback module is adapted to return a response to the abnormal event to the server, and when the response is to set an alternative execution time for the coping operation, instruct the server to execute the associated virtual machine at the alternative execution time. Describe coping actions. 16.一种计算设备,包括:16. A computing device comprising: 至少一个处理器;和at least one processor; and 存储有程序指令的存储器,其中,所述程序指令被配置为适于由所述至少一个处理器执行,所述程序指令包括用于执行如权利要求1-13中任一项所述方法的指令。a memory storing program instructions, wherein the program instructions are configured to be adapted for execution by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-13 . 17.一种存储有程序指令的可读存储介质,当所述程序指令被计算设备读取并执行时,使得所述计算设备执行如权利要求1-13中任一项所述的方法。17. A readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the method of any one of claims 1-13.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811120304.6A CN110928714A (en) | 2018-09-19 | 2018-09-19 | A service exception processing method, device and computing device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811120304.6A CN110928714A (en) | 2018-09-19 | 2018-09-19 | A service exception processing method, device and computing device |
Publications (1)
Publication Number | Publication Date |
---|---|
CN110928714A true CN110928714A (en) | 2020-03-27 |
Family
ID=69856383
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201811120304.6A Pending CN110928714A (en) | 2018-09-19 | 2018-09-19 | A service exception processing method, device and computing device |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110928714A (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN86103695A (en) * | 1985-08-16 | 1987-02-11 | 惠普公司 | The method and apparatus that is used for fault recovery in the computing system |
CN106559441A (en) * | 2015-09-25 | 2017-04-05 | 华为技术有限公司 | It is a kind of based on the virtual machine monitoring method of cloud computing service, apparatus and system |
US20170199795A1 (en) * | 2016-01-08 | 2017-07-13 | Microsoft Technology Licensing, Llc | Deferred server recovery in computing systems |
CN108519940A (en) * | 2018-04-12 | 2018-09-11 | 郑州云海信息技术有限公司 | A kind of storage device alarm method, system and computer readable storage medium |
-
2018
- 2018-09-19 CN CN201811120304.6A patent/CN110928714A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN86103695A (en) * | 1985-08-16 | 1987-02-11 | 惠普公司 | The method and apparatus that is used for fault recovery in the computing system |
CN106559441A (en) * | 2015-09-25 | 2017-04-05 | 华为技术有限公司 | It is a kind of based on the virtual machine monitoring method of cloud computing service, apparatus and system |
US20170199795A1 (en) * | 2016-01-08 | 2017-07-13 | Microsoft Technology Licensing, Llc | Deferred server recovery in computing systems |
CN108369544A (en) * | 2016-01-08 | 2018-08-03 | 微软技术许可有限责任公司 | Deferred server recovery in a computing system |
CN108519940A (en) * | 2018-04-12 | 2018-09-11 | 郑州云海信息技术有限公司 | A kind of storage device alarm method, system and computer readable storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10838803B2 (en) | 2020-11-17 | Resource provisioning and replacement according to a resource failure analysis in disaggregated data centers |
KR101888029B1 (en) | 2018-09-11 | Method and system for monitoring virtual machine cluster |
US9335998B2 (en) | 2016-05-10 | Multi-core processor system, monitoring control method, and computer product |
US10785320B2 (en) | 2020-09-22 | Managing operation of instances |
CN108369544B (en) | 2021-06-22 | Deferred server recovery in a computing system |
US11048577B2 (en) | 2021-06-29 | Automatic correcting of computing cluster execution failure |
US11327767B2 (en) | 2022-05-10 | Increasing resources for partition to compensate for input/output (I/O) recovery event |
CN113064744A (en) | 2021-07-02 | Task processing method and device, computer readable medium and electronic equipment |
US10891206B2 (en) | 2021-01-12 | Disaster recovery orchestration and capacity planning in disaggregated datacenters |
CN113886089A (en) | 2022-01-04 | Task processing method, device, system, equipment and medium |
US20240265031A1 (en) | 2024-08-08 | Preventing data loss in event driven continuous availability systems |
US11036599B2 (en) | 2021-06-15 | Disaster recovery and replication according to workload priorities in disaggregated datacenters |
US20200151049A1 (en) | 2020-05-14 | Increasing processing capacity of processor cores during initial program load processing |
TWI734348B (en) | 2021-07-21 | Computer implement method, system and program product for increasing processing capacity of virtual machines for an abnormal event |
JP5695420B2 (en) | 2015-04-08 | Method, system, and computer program for scheduling execution of jobs driven by events |
CN110928714A (en) | 2020-03-27 | A service exception processing method, device and computing device |
US10719418B2 (en) | 2020-07-21 | Replicating workload data according to a degree of resiliency for disaster recovery in disaggregated datacenters |
US20230088318A1 (en) | 2023-03-23 | Remotely healing crashed processes |
US11487587B2 (en) | 2022-11-01 | Information processing system and method for controlling information processing system |
Fé et al. | 2024 | Energy-aware dynamic response and efficient consolidation strategies for disaster survivability of cloud microservices architecture |
Tandon et al. | 2024 | Fault tolerant and reliable resource optimization model for cloud |
CN112632033B (en) | 2025-01-24 | Cluster data migration method, device and electronic equipment |
US20230044503A1 (en) | 2023-02-09 | Distribution of workloads in cluster environment using server warranty information |
JP2017068668A (en) | 2017-04-06 | Database system, replication controller, replication method and program |
CN117149381A (en) | 2023-12-01 | Distributed task management method, system, computing device and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
2020-03-27 | PB01 | Publication | |
2020-03-27 | PB01 | Publication | |
2020-06-05 | SE01 | Entry into force of request for substantive examination | |
2020-06-05 | SE01 | Entry into force of request for substantive examination | |
2021-01-15 | REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40026848 Country of ref document: HK |
2024-12-03 | RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200327 |
2024-12-03 | RJ01 | Rejection of invention patent application after publication |