# US 2012/0254669 A1 · Proactive failure handling in database services

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

- Number: US 2012/0254669 A1
- Document ID: US20120254669A1
- Status: Published application
- Kind: A1
- Application number: 13/079,750
- Filed: 2011-04-04
- Published: 2012-10-04
- Earliest claimed: 2011-04-04
- Assignees: Microsoft Corporation
- Inventors: Hao Xia; Todd F. Pfleiger; Mark C. Benvenuto; Ajay Kalhan
- Web page: https://patentgrep.com/patent/US20120254669A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/004: {Error avoidance (G06F11/07 and subgroups take precedence)}
- 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/076: {by exceeding a count or rate limit, e.g. word- or bit count limit}
- G06F 11/0769: {Readable error formats, e.g. cross-platform generic formats, human understandable formats}
- G06F 11/0787: {Storage of error reports, e.g. persistent data storage, storage using memory protection}
- G06F 11/2257: {using expert systems}
- 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)}
- 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)}
- G06F 11/3065: {Monitoring arrangements determined by the means or processing involved in reporting the monitored data (error or fault reporting or logging G06F11/0766)}
- G06F 11/324: {Display of status information}
- H04L 43/065: related to network devices
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments are directed to predicting the health of a computer node using health report data and to proactively handling failures in database services. In an embodiment, a computer system monitors various health indicators for multiple nodes in a database cluster. The computer system accesses stored health indicators that provide a health history for the database cluster nodes. The computer system then generates a health status based on the monitored health factors and the health history. The generated health status indicates the likelihood that the node will be healthy within a specified future time period. The computer system then leverages the generated health status to handle current or predicted failures. The computer system also presents the generated health status to a user or other entity.

## Claims

### Claim 1

At a computer system including at least one processor and a memory, in a computer networking environment including a plurality of computing systems, a computer-implemented method for predicting the health of a computer node using health report data, the method comprising:
an act of monitoring one or more health indicators for a plurality of nodes in a database cluster;
an act of accessing one or more stored health indicators that provide a health history for the database cluster nodes;
an act of generating a health status based on the monitored health factors and the health history, wherein the generated health status indicates the likelihood that the node will be healthy within a specified future time period; and
an act of presenting the generated health status to a specified entity.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining, for at least one of the monitored nodes, that the likelihood that the node will be healthy is below a threshold level; and
transferring one or more portions of data stored on the monitored node to one or more other nodes in the database cluster.

### Claim 3 (depends on 2)

The method of claim 2, further comprising preventing the monitored node from storing new data.

### Claim 4 (depends on 2)

The method of claim 2, wherein the determination that the likelihood that node will be healthy is below a threshold level comprises determining that the monitored node is in a critical state.

### Claim 5 (depends on 2)

The method of claim 2, wherein the determination that the likelihood that node will be healthy is below a threshold level comprises determining that the monitored node has experienced one or more failures within a specified time period.

### Claim 6 (depends on 5)

The method of claim 5, further comprising assigning an error level to each of the failures.

### Claim 7 (depends on 6)

The method of claim 6, further comprising determining that a threshold number of the failures are beyond a specified error level, such that the monitored node is blacklisted.

### Claim 8 (depends on 7)

The method of claim 7, wherein nodes that have a threshold number of the failures beyond a specified error level are blacklisted, regardless of the node's health history.

### Claim 9 (depends on 7)

The method of claim 7, wherein blacklisted nodes are put on probation for a specified amount of time to determine whether errors occur during probation.

### Claim 10 (depends on 9)

The method of claim 9, wherein upon determining that the probationary period is complete and that no further errors have occurred, allowing the monitored node to continue storing new data and removing the monitored node from the blacklist.

### Claim 11 (depends on 9)

The method of claim 9, wherein upon determining that the probationary period is complete and that one or more further errors have occurred, preventing the monitored node from storing new data.

### Claim 12 (depends on 11)

The method of claim 11, further comprising relocating data portions that are hosted on the monitored node.

### Claim 13

A computer program product for implementing a method for proactively handling failures in database services, the computer program product comprising one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of the computing system, cause the computing system to perform the method, the method comprising:
an act of monitoring one or more health indicators for a plurality of nodes in a database cluster;
an act of accessing one or more stored health indicators that provide a health history for the database cluster nodes;
an act of generating a health status based on the monitored health factors and the health history, wherein the generated health status indicates the likelihood that the node will be healthy within a specified future time period;
an act of determining, for at least one of the monitored nodes, that a threshold number of failures have occurred that are beyond a specified error level, such that the monitored node is blacklisted;
an act of transferring one or more portions of data stored on the monitored node to one or more other nodes in the database cluster; and
an act of preventing the monitored node from storing new data.

### Claim 14 (depends on 13)

The computer program product of claim 13, wherein the monitored node is categorized as up and blacklisted, such that the node remains used for storing data while the data is transferred to other nodes, and no new data is stored on the monitored node.

### Claim 15 (depends on 13)

The computer program product of claim 13, wherein the monitored node is categorized as down and blacklisted, such that the node is no longer used for storing data, the data is transferred to other nodes, and no new data is stored on the monitored node.

### Claim 16 (depends on 15)

The computer program product of claim 15, wherein the data is transferred without waiting for a probationary period.

### Claim 17

A computer system comprising the following:
one or more processors;
system memory;
one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for proactively handling failures in database services, the method comprising the following:
an act of monitoring one or more health indicators for a plurality of nodes in a database cluster;
an act of accessing one or more stored health indicators that provide a health history for the database cluster nodes;
an act of generating a health status based on the monitored health factors and the health history, wherein the generated health status indicates the likelihood that the node will be healthy within a specified future time period; and
an act of presenting the generated health status to a specified entity.

### Claim 18 (depends on 17)

The system of claim 17, further comprising an act of blacklisting at least one of the monitored nodes upon determining that a threshold number of failures have occurred that are beyond a specified error level.

### Claim 19 (depends on 18)

The system of claim 18, further comprising an act of transferring one or more portions of data stored on the monitored node to one or more other nodes in the database cluster.

### Claim 20 (depends on 19)

The system of claim 19, wherein the monitored node is categorized as up and blacklisted, such that the node remains used for storing data while the data is transferred to other nodes, and no new data is stored on the monitored node.
