Distributed system, server computer, distributed management server, and failure prevention method

Patent metadata

Field	Value
Publication number	US-10157110-B2
Application number	US-201615096422-A
Country	US
Kind code	B2
Filing date	Apr 12, 2016
Priority date	Sep 24, 2012
Publication date	Dec 18, 2018
Grant date	Dec 18, 2018

Abstract

A distributed system according to an exemplary embodiment includes first and second servers capable of executing the same application, wherein when a failure occurs in the application in the first server, the first server generates failure information identifying a cause of the failure in the application, and the second server performs failure prevention processing which is determined based on the failure information and intended to prevent a failure in the application.

First claim

What is claimed is:

1. A system comprising:
a first server configured to run a first application, the first server configured to send information related to a failure of the first server to a second server upon the first application running on the first server failing; and
the second server configured to run a second application which is different from the first application, the second server configured to perform failure prevention processing based on the information to prevent a related failure in the second application running on the second server,
wherein the second server, which is configured to perform the failure prevention processing, is configured to monitor the state of the second server every predetermined time after receiving the information from the first server to determine whether the second server executes the failure prevention processing.

2. The system according to claim 1 , wherein the information related to a failure of the first server indicates one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure.

3. The system according to claim 1 , wherein the second server is configured to monitor requests to the second application, as well as to control the order or timing of execution of the requests based on the information.

4. A server, wherein
the server is configured to receive, from a different server from the server configured to run a first application, information related to a failure of the different server upon the first application running on the different server failing;
the server is configured to run a second application which is different from the first application; and
the server is configured to perform failure prevention processing based on the information to prevent a related failure in the second application running on the server,
wherein the server, which is configured to perform the failure prevention processing, is configured to monitor the state of the server every predetermined time after receiving the information from the different server to determine whether the server executes the failure prevention processing.

5. The server according to claim 4 , wherein the server is configured to monitor the state of the server every predetermined time after receiving the information from the different server to determine whether the server executes the failure prevention processing.

6. The server according to claim 4 , wherein the information related to a failure of the different server indicates one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure.

7. The server according to claim 4 , wherein the server is configured to monitor requests to the second application, as well as to control the order or timing of execution of the requests based on the information.

8. A method comprising:
running, by a first server, a first application;
running, by a second server, a second application which is different from the first application;
sending, by the first server, information related to a failure of the first server to the second server upon the first application running on the first server failing;
monitoring, by the second server that is configured to perform the failure prevention processing, the state of the second server every predetermined time after receiving the information from the first server to determine whether the second server executes the failure prevention processing; and
performing, by the second server, failure prevention processing based on the information to prevent a related failure in the second application running on the second server.

9. The method according to claim 8 , wherein the information related to a failure of the first server indicates one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure.

10. The method according to claim 8 , further comprising:
monitoring, by the second server, requests to the second application, as well as controlling the order or timing of execution of the requests based on the information.

11. A method performed by a server, comprising:
receiving, from a different server configured to run a first application, information related to a failure of the different server upon the first application running on the different server failing;
running a second application which is different from the first application;
monitoring, by the server that is configured to perform the failure prevention processing, the state of the server every predetermined time after receiving the information from the different server to determine whether the server executes the failure prevention processing; and
performing failure prevention processing based on the information to prevent a related failure in the second application running on the server.

12. The method according to claim 11 , wherein the information related to a failure of the different server indicates one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure.

13. The method according to claim 11 , further comprising:
monitoring requests to the second application, as well as controlling the order or timing of execution of the requests based on the information.

14. A non-transitory computer readable medium storing a program that causes a server to execute:
a step of receiving, from a different server from the server configured to run a first application, information related to a failure of the different server upon the first application running on the different server failing;
a step of running a second application which is different from the first application;
a step of monitoring, by the server that is configured to perform the failure prevention processing, the state of the server every predetermined time after receiving the information from the different server to determine whether the server executes the failure prevention processing; and
a step of performing failure prevention processing based on the information to prevent a related failure in the second application running on the server.

15. The non-transitory computer readable medium storing the program according to claim 14 , wherein the information related to a failure of the different server indicates one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure.

16. The non-transitory computer readable medium storing the program according to claim 14 , the program further causing the server to execute:
a step of monitoring requests to the second application, as well as controlling the order or timing of execution of the requests based on the information.

Assignees

• Nec Corp

Inventors

• Okada Yoshihiro

Classifications

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title

• G06F11/076

  by exceeding a count or rate limit, e.g. word- or bit count limit · CPC title

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• G06F11/0715

  in a system implementing multitasking (multitasking per se G06F9/46) · CPC title

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title