# US 2014/0208173 A1 · Common lease agent for cluster communication

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

- Number: US 2014/0208173 A1
- Document ID: US20140208173A1
- Status: Published application
- Kind: A1
- Application number: 13/745,216
- Filed: 2013-01-18
- Published: 2014-07-24
- Earliest claimed: 2013-01-18
- Assignees: Microsoft Corporation
- Applicants: Microsoft Corporation
- Inventors: Lu Xun; Mihail Gavril Tarta; Yang Li; Gopala Krishna R. Kakivaya
- Web page: https://patentgrep.com/patent/US20140208173A1

## CPC

- G06F 11/006: {Identification (G06F11/2289 takes precedence)}
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- 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

Detecting failures of interconnected machines. A method includes establishing a machine to machine lease at a first machine using a first lease agent at the first machine to a second lease agent at a second machine as a result of an application on the first machine requesting to establish a lease with an application on the second machine. Using the machine to machine lease, the method further includes detecting a communication failure between the first machine and the second machine or a machine failure of the second machine.

## Claims

### Claim 1

A method of detecting failures of interconnected machines, the method comprising:
establishing a machine to machine lease at a first machine using a first lease agent at the first machine to a second lease agent at a second machine as a result of an application on the first machine requesting to establish a lease with an application on the second machine; and
using the machine to machine lease, detecting a communication failure between the first machine and the second machine or a machine failure of the second machine.

### Claim 2 (depends on 1)

The method of claim 1, further comprising as a result of detecting a communication failure between the first machine and the second machine or a machine failure of the second machine, submitting to arbitration to have an arbitrator decide if applications at the first machine or the second machine should go down.

### Claim 3 (depends on 1)

The method of claim 1, further comprising registering a single application instance on the first machine to a plurality of different lease agents on the first machine such than any of the lease agents in the plurality of lease agents can indicate to the application instance that the application instance should go down.

### Claim 4 (depends on 3)

The method of claim 3, wherein each of the lease agents in the plurality of lease agents is configured to detect different types of application or machine failures.

### Claim 5 (depends on 3)

The method of claim 3, wherein the single application instance on the first machine going down is visible to all of the lease agents in the plurality of different lease agents on the first machine such that the lease agents on the first machine can indicate that the application is down on lease agents on other machines.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first machine stores a subject list, wherein the subject list comprises a collection of application level monitoring relationships where the applications on the first machine act as a subject, wherein each relationship identifies both a local application instance on the first machine and a remote application instance on the second machine.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first machine stores a pending list as an optimization to avoiding sending the subject list to the second machine repeatedly, wherein the pending list contains the subject relationships that need to be established or terminated but that are not yet acknowledged by the second machine.

### Claim 8 (depends on 7)

The method of claim 7, wherein the first machine stores a monitor list as an optimization to avoiding sending the subject list to the second machine repeatedly, wherein the monitor list contains the monitor relationships that need to be established or terminated but that are not yet acknowledged by the second machine.

### Claim 9 (depends on 8)

The method of claim 8, wherein the first machine stores a failure list, the failure list comprising a collection of local failed application instances that appear in either the subject list, the pending list, or the monitor list.

### Claim 10

A method of detecting failures of interconnected machines, the method comprising:
establishing a machine to machine lease at a first machine using a first lease agent at the first machine as the result of a first application instance on the first machine requesting to establish a lease with a second application instance; and
using the lease detecting an application failure of the second application instance.

### Claim 11 (depends on 10)

The method of claim 10, wherein the machine to machine lease is a lease between the first machine and itself using the same first lease agent, wherein the first application instance and the second application instance both register with the first lease agent.

### Claim 12 (depends on 10)

The method of claim 10, wherein the machine to machine lease is a lease between the first machine and itself using two different lease agents on the first machine where the first application instance registers with the first lease agent on the first machine and the second application instance registers with a second lease agent on the first machine, and wherein the first and second lease agents communicate with each other.

### Claim 13 (depends on 10)

The method of claim 10, wherein the machine to machine lease is a lease between the first machine and a second machine using the first lease agent on the first machine and a second lease agent on the second machine, where the first application instance registers with the first lease agent on the first machine and the second application instance registers with a second lease agent on the second machine, and wherein the first and second lease agents communicate with each other.

### Claim 14

A system for detecting failures of interconnected machines, the system comprising:
one or more processors; and
one or more computer readable media, wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one of the processors cause the system to perform the following:
establishing a machine to machine lease at a first machine using a first lease agent at the first machine to a second lease agent at a second machines as a result of an application on the first machine requesting to establish a lease with an application on the second machine; and
using the machine to machine lease, detecting a communication failure between the first machine and the second machine or a machine failure of the second machine.

### Claim 15 (depends on 14)

The system of claim 14, wherein the computer readable media further comprise computer executable instructions that when executed by at least one of the processors cause the system to: as a result of detecting a communication failure between the first machine and the second machine or a machine failure of the second machine, submit to arbitration to have an arbitrator decide if applications at the first machine or the second machine should go down.

### Claim 16 (depends on 14)

The system of claim 14, wherein the computer readable media further comprise computer executable instructions that when executed by at least one of the processors cause the system to register a single application instance on the first machine to a plurality of different lease agents on the first machine such than any of the lease agents in the plurality of lease agents can indicate to the application instance that the application instance should go down.

### Claim 17 (depends on 14)

The system of claim 14, wherein the first machine stores a subject list, wherein the subject list comprises a collection of application level monitoring relationships where the applications on the first machine act as a subject, wherein each relationship identifies both a local application instance on the first machine and a remote application instance on the second machine.

### Claim 18 (depends on 17)

The system of claim 17, wherein the first machine stores a pending list as an optimization to avoiding sending the subject list to the second machine repeatedly, wherein the subject list contains the subject relationships that need to be established or terminated but that are not yet acknowledged by the second machine.

### Claim 19 (depends on 18)

The system of claim 18, wherein the first machine stores a monitor list as an optimization to avoiding sending the subject list to the second machine repeatedly, wherein the monitor list contains the monitor relationships that need to be established or terminated but that are not yet acknowledged by the second machine.

### Claim 20 (depends on 19)

The system of claim 19, wherein the first machine stores a failure list, the failure list comprising a collection of local failed application instances that appear in either the subject list, the pending list, or the monitor list.
