# US 2012/0254652 A1 · Fault detection and recovery as a service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254652 A1
- Document ID: US20120254652A1
- Status: Published application
- Kind: A1
- Application number: 13/076,963
- Filed: 2011-03-31
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Microsoft Corporation
- Inventors: Atul Katiyar; Chinna Babu Polinati
- Web page: https://patentgrep.com/patent/US20120254652A1

## CPC

- H04L 43/12: Network monitoring probes
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/1438: {Restarting or rejuvenating}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/203: {using migration}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- H04L 41/0695: the faulty arrangement being the maintenance, administration or management system
- G06F 11/2025: {using centralised failover control functionality}
- G06F 11/2035: {without idle spare hardware}
- G06F 11/3055: {Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The monitoring by a monitoring node of a process performed by a monitored node is often devised as a tightly coupled interaction, but such coupling may reduce the re-use of monitoring resources and processes and increase the administrative complexity of the monitoring scenario. Instead, fault detection and recovery may be designed as a non-proprietary service, wherein a set of monitored nodes, together performing a set of processes, may register for monitoring by a set of monitoring nodes. In the event of a failure of a process, or of an entire monitored node, the monitoring nodes may collaborate to initiate a restart of the processes on the same or a substitute monitored node (possibly in the state last reported by the respective processes). Additionally, failure of a monitoring node may be detected, and all monitored nodes assigned to the failed monitoring node may be reassigned to a substitute monitoring node.

## Claims

### Claim 1

A method of configuring a monitoring node having a processor to monitor monitored nodes executing at least one process, the method comprising:
executing on the processor instructions configured to:
upon receiving a request to monitor a monitored node, register at least one process of the monitored node for monitoring;
upon receiving at least one status from a process of a monitored node, record the status of the process; and
upon detecting a failure of at least one process of a monitored node, restart the process on a monitored node.

### Claim 2 (depends on 1)

The method of claim 1:
at least one monitored node configured to send to the monitoring node, within a notification period, a persistence indicator; and
detecting a failure comprising: detecting an elapsing of a notification period without having received a persistence indicator from the monitored node.

### Claim 3 (depends on 1)

The method of claim 1:
the monitoring node monitoring at least two monitored nodes; and
restarting at least one process on a monitored node comprising:
selecting a substitute monitored node, and
restarting at least one process of the monitored node on the substitute monitored node.

### Claim 4 (depends on 3)

The method of claim 3:
detecting a failure of at least one process of a monitored node comprising: detecting a failure of a monitored node; and
restarting the least one process on the monitored node comprising: restarting all processes of the monitored node on the substitute monitored node.

### Claim 5 (depends on 1)

The method of claim 1:
at least one process of a monitored node configured to report to the monitoring node at least one state of at least one process; and
the instructions configured to, upon receiving a report of a state of at least one process reported by a monitored node, store the state of the process.

### Claim 6 (depends on 5)

The method of claim 5, restarting a process on a monitored node comprising: restarting the process on a monitored node at the state last reported by the process.

### Claim 7 (depends on 5)

The method of claim 5:
the monitoring node comprising a logic to be performed when a process reports a particular state; and
the instructions configured to, upon receiving a report of the particular state from a process, performing the logic.

### Claim 8 (depends on 7)

The method of claim 7, the instructions configured to, upon receiving a logic from a monitored node to be performed when a process of the monitored node reports a particular state, store the logic.

### Claim 9 (depends on 1)

The method of claim 1, the monitoring node included in a monitoring node set comprising at least one other monitoring node.

### Claim 10 (depends on 9)

The method of claim 9:
the monitoring nodes of the monitoring node set configured to store at least one status of at least one monitored node; and
the instructions configured to synchronize the at least one status of at least one monitored node with at least one other monitoring node of the monitoring node set.

### Claim 11 (depends on 9)

The method of claim 9:
detecting a failure of at least one process of a monitored node comprising: detecting a failure of a monitored node; and
restarting the least one process on the monitored node comprising: conferring with at least one other monitoring node of the monitoring node set to choose a substitute monitored node for the monitored node.

### Claim 12 (depends on 9)

The method of claim 9, respective monitored nodes assigned for monitoring by at least one monitoring node of the monitoring node set.

### Claim 13 (depends on 12)

The method of claim 12, registering at least one process of a monitored node for monitoring comprising: conferring with at least one other monitoring node of the monitoring node set to choose a monitoring node for monitoring the monitored node.

### Claim 14 (depends on 9)

The method of claim 9, the instructions configured to detect a failure of a second monitoring node.

### Claim 15 (depends on 14)

The method of claim 14:
the second monitoring node configured to send to the monitoring node, within a notification period, a persistence indicator; and
detecting the failure of the second monitoring node comprising: detecting an elapsing of a notification period without having received a persistence indicator from the second monitoring node.

### Claim 16 (depends on 14)

The method of claim 14, detecting the failure of the second monitoring node comprising: receiving from a monitored node a failure indicator of the second monitoring node.

### Claim 17 (depends on 14)

The method of claim 14:
respective monitored nodes assigned for monitoring by at least one monitoring node of the monitoring node set; and
the instructions configured to, upon detecting the failure of a second monitoring node to which at least one monitored node is assigned:
choose a substitute monitoring node, and
reassign the at least one monitored node to the substitute monitoring node.

### Claim 18 (depends on 17)

The method of claim 17, choosing a substitute monitoring node for at least one monitored node comprising: conferring with at least one other monitoring node of the monitoring node set to choose a substitute monitoring node for the monitored node.

### Claim 19

A method of configuring a monitored node executing at least one process on a processor to be monitored by a monitored node, the method comprising:
executing on the processor instructions configured to:
register at least one process with the monitoring node;
report at least one status of at least one process to a monitoring node; and
upon receiving from a monitoring node a request to restart a process, restart the process.

### Claim 20

A computer-readable storage medium comprising instructions that, when executed on a processor of a monitoring node of a monitoring node set, cause the monitoring node to monitor at least two monitored nodes respectively executing at least one process comprising a logic to be performed when the process reports a particular state, respective processes configured to report to the monitoring node at least one state and to send to the monitoring node, within a notification period, a persistence indicator, by:
upon receiving a request to monitor a monitored node, registering at least one process of the monitored node for monitoring;
upon receiving a logic from a monitored node to be performed when a process of the monitored node reports a particular state, store the logic;
upon receiving a report of a state of at least one process reported by a monitored node, store the state of the process;
upon receiving from a process a report of a particular state associated with a logic for the process, performing the logic;
synchronizing the one states of respective processes at least one monitored node with at least one other monitoring node of the monitoring node set;
upon detecting a failure of at least one process of a monitored node, the failure comprising an elapsing of a notification period without having received a persistence indicator from the monitored node, restarting the process on a monitored node at the state last reported by the process;
upon detecting a failure of a monitored node:
conferring with at least one other monitoring node of the monitoring node set to choose a substitute monitored node for the monitored node to choose a substitute monitored node, and
restarting the least one process on the monitored node comprising: restarting respective processes of the monitored node at the state last reported by the process on a substitute monitored node;
sending to at least one other monitoring node, within a notification period, a persistence indicator;
upon detecting an elapsing of a notification period without having received a persistence indicator from the second monitoring node:
conferring with at least one other monitoring node of the monitoring node set to choose a substitute monitoring node for the monitored node, and
reassigning the at least one monitored node to the substitute monitoring node.
