# US 2025/0086068 A1 · Failure recovery in a scaleout system using vector clock

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

- Number: US 2025/0086068 A1
- Document ID: US20250086068A1
- Status: Published application
- Kind: A1
- Application number: 18/464,726
- Filed: 2023-09-11
- Published: 2025-03-13
- Earliest claimed: 2023-09-11
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Keyur B. Desai
- Web page: https://patentgrep.com/patent/US20250086068A1

## CPC

- G06F 11/1469: {Backup restoration techniques}
- G06F 11/08: Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F 11/1471: involving logging of persistent data for recovery
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- 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

Determining a failure recovery line in a distributed scaleout computing system. Each node or process of a distributed system has or is associated with a vector clock that includes a logical clock for each node in the distributed system. When failure is detected, a recovery operation may be performed using the vector clock. After the recovery operation, the vector clock is updated such that the failure recovery line is available in the computing system.

## Claims

### Claim 1

A method comprising:
associating a vector clock with each node in a distributed scaleout system;
when an event occurs at a node, updating a vector clock associated with the node;
determining a failure in the distributed scaleout system;
performing a rollback operation using the vector clocks, wherein the vector clocks identify a failure recovery line for recovering the distributed scaleout system from the failure; and
performing a recovery operation based on the failure recovery line.

### Claim 2 (depends on 1)

The method of claim 1, wherein each of the vector clocks includes a home logical clock for a corresponding node and one or more away logical clocks for other nodes in the distributed Scaleout system.

### Claim 3 (depends on 1)

The method of claim 1, wherein the event is an internal event, further comprising updating the home logical clock in the vector clock of the node that experienced the internal event.

### Claim 4 (depends on 1)

The method of claim 1, wherein the event is an external event, further comprising updating a home logical clock in the vector clock of the node and updating the vector clock of the node based using a vector clock of a sending node that sent the event to the node.

### Claim 5 (depends on 1)

The method of claim 1, further comprising performing a cascaded rollback operation using the vector clocks.

### Claim 6 (depends on 5)

The method of claim 5, wherein the recovery operation includes recovering from a snapshot and replaying logs, wherein the logs store a chronological history of events in the distributed scaleout system.

### Claim 7 (depends on 6)

The method of claim 6, further comprising updating the vector clocks such that the vector clocks include a failure recovery line that accounts for the recovery operation.

### Claim 8 (depends on 7)

The method of claim 7, wherein some entries in the vector clocks are deleted and replaced with new entries.

### Claim 9 (depends on 1)

The method of claim 1, further comprising scaling the distributed computing system, wherein a vector clock of a new node added to the distributed computing system is initialized to zeros.

### Claim 10 (depends on 1)

The method of claim 1, further comprising moving multiple nodes forward from a recovery line after using the failure recovery line to identify the recovery line.

### Claim 11

A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
associating a vector clock with each node in a distributed scaleout system;
when an event occurs at a node, updating a vector clock associated with the node;
determining a failure in the distributed scaleout system;
performing a rollback operation using the vector clocks, wherein the vector clocks identify a failure recovery line for recovering the distributed scaleout system from the failure; and
performing a recovery operation based on the failure recovery line.

### Claim 12 (depends on 11)

The non-transitory storage medium of claim 11, wherein each of the vector clocks includes a home logical clock for a corresponding node and one or more away logical clocks for other nodes in the distributed Scaleout system.

### Claim 13 (depends on 11)

The non-transitory storage medium of claim 11, wherein the event is an internal event, further comprising updating the home logical clock in the vector clock of the node that experienced the internal event.

### Claim 14 (depends on 11)

The non-transitory storage medium of claim 11, wherein the event is an external event, further comprising updating a home logical clock in the vector clock of the node and updating the vector clock of the node based using a vector clock of a sending node that sent the event to the node.

### Claim 15 (depends on 11)

The non-transitory storage medium of claim 11, further comprising performing a cascaded rollback operation using the vector clocks.

### Claim 16 (depends on 15)

The non-transitory storage medium of claim 15, wherein the recovery operation includes recovering from a snapshot and replaying logs, wherein the logs store a chronological history of events in the distributed scaleout system.

### Claim 17 (depends on 16)

The non-transitory storage medium of claim 16, further comprising updating the vector clocks such that the vector clocks include a failure recovery line that accounts for the recovery operation.

### Claim 18 (depends on 17)

The non-transitory storage medium of claim 17, wherein some entries in the vector clocks are deleted and replaced with new entries.

### Claim 19 (depends on 11)

The non-transitory storage medium of claim 11, further comprising scaling the distributed computing system, wherein a vector clock of a new node added to the distributed computing system is initialized to zeros.

### Claim 20 (depends on 11)

The non-transitory storage medium of claim 11, further comprising moving multiple nodes forward from a recovery line after using the failure recovery line to identify the recovery line.
