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

Patent metadata

Field	Value
Publication number	US-9342426-B2
Application number	US-201314035311-A
Country	US
Kind code	B2
Filing date	Sep 24, 2013
Priority date	Sep 24, 2012
Publication date	May 17, 2016
Grant date	May 17, 2016

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 an application, the first server configured to generate failure information identifying a cause of the failure in the application upon the application running on the first server failing, the failure information indicating one or more of:
a component of the application that caused the failure;
an interface associated with the component that caused the failure;

a second server configured to run the application, the second server configured to perform failure prevention processing based on the failure information to prevent a corresponding failure in the application running on the second server.

2. The system of claim 1 , further comprising:
a distributed management server configured to manage the first and second servers,
wherein the failure information includes information identifying recovery processing for the first server to recover from the failure,
wherein the distributed management server is configured to extract the information from the failure information and transmits the information to the first server,
and wherein the first server is configured to perform the recover processing received from the distributed management server.

3. The system of claim 1 , wherein the failure in the application results from a request from a client of the first server,
and wherein the second server is configured to monitor a request from a client of the second server based on the failure information.

4. The system of claim 3 , wherein the component is a first component, the interface is a first interface of the first component, and the first interface has a highest number of failures of any interface of any component,
wherein when the failure pertains to the first interface and is greater than a threshold, the first server is configured to identify the first interface as the cause of the failure, and is configured to output the failure information as including a second interface of a second component, the second interface having a second highest number of failures of any interface of any component,
and wherein in response to receiving a request from a client of the first interface and in response to determining that the second interface is being executed, the second server is configured to prevent processing of the request.

5. The system of claim 3 , wherein the component is a first component, the interface is a first interface of the first component,
wherein when the failure pertains to the first interface and is greater than a threshold and when another failure pertains to a second interface of a second component and is greater than the threshold, the first server is configured to identify the first interface as the cause of the failure, and is configured to output the failure information as including a second interface of a second component,
and wherein in response to receiving a request from a client and in response to determining that the second interface is being executed, the second server is configured to prevent processing of the request.

6. The system of claim 4 , wherein in response to receiving another request from the client and in response to determining that the first interface is being executed, the second server is configured to prevent processing of the another request.

7. The system of claim 3 , wherein the component is a first component, the interface is a first interface of the first component,
wherein when a deadlock between the first interface and a second interface of a second component is the failure, the first server is configured to output the failure information identifying the first and second interfaces as the cause of the failure,
and wherein in response to receiving a request from a client of the first interface and in response to determining that the second interface is being executed, the second server is configured to prevent processing of the request.

8. A server comprising:
a networking interface configured to communicatively connect with another server within a distributed system;
a processor configured to run an application; and
a storage device storing computer-executable code that the processor executes to:
in response to a failure occurring in the application, generate failure information identifying a cause of the failure as one or more of:
a component of the application that caused the failure; and
an interface associated with the component that caused the failure;

upon the another server generating different failure information identifying a cause of a failure occurring in the application as run by the another server, perform failure prevention processing based on the different information to prevent a corresponding failure in the application running on the server.

9. A server comprising:
a networking interface configured to communicatively connect with a first server and a second server within a distributed system, each of the first and second servers configured to run an application, the server managing the first and second servers;
a processor; and
a storage device storing computer-executable code that the processor executes to, upon the application failing on the first server, receiving failure information generated by the first server that identifies a cause of the failure as one or more of:
a component of the application that caused the failure; and
an interface associated with the component that caused the failure,

wherein the second server is further to receive the failure information and is to perform failure prevention processing based on the failure information to prevent a corresponding failure in the application running on the second server.

10. A method comprising:
running, by a first server, an application;
running, by a second server, the application;
in response to failure occurring in the application at the first server, identifying, by the first server, a cause of the failure as one or more of:
a component of the application that caused the failure; and
an interface associated with the component that caused the failure;

receiving, by the second server, the failure information; and
performing, by the second server, failure prevention processing based on the failure information to prevent a corresponding failure in the application running on the second server.

11. The system of claim 1 , wherein the component is a first component, the interface is a first interface of the first component,
wherein when the failure pertains to the first interface and to a second interface of a second component, the first server is configured to output the failure information as including the first and second interfaces,
and wherein in response to receiving a request from a client of the first interface and in response to determining that the second interface is being executed, the second server is configured to prevent processing of the request.

Assignees

• Nec Corp

Inventors

• Okada Yoshihiro

Classifications

• G06F11/076

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

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · 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/2736 Primary

  using a dedicated service processor for test · CPC title

• G06F11/0709 Primary

  in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title