# US 2026/0220000 A1 · Performing bucket recovery operations

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

- Number: US 2026/0220000 A1
- Document ID: US20260220000A1
- Status: Published application
- Kind: A1
- Application number: 19/574,062
- Filed: 2026-03-20
- Published: 2026-07-30
- Earliest claimed: 2024-04-30
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Sayantan BHATTACHARYYA; Wendi QIU; Christopher Michael SUTTON
- Web page: https://patentgrep.com/patent/US20260220000A1

## CPC

- G06F 11/1464: {for networked environments}
- G06F 11/1469: {Backup restoration techniques}
- H04L 67/1074: for supporting data block transmission mechanisms (file transfer H04L67/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

A method for recovering corrupted buckets in a peer cluster is presented. A cluster manager sends a request to peer nodes storing bucket copies corresponding to a corrupted bucket to report bucket health metrics of the respective bucket copies. The peer nodes rebuild the respective bucket copies and report updated bucket health metrics corresponding to the respective rebuilt bucket copies to the cluster manager. The cluster manager elects a bucket copy with a highest searchable event count as the canonical bucket copy. The cluster manager sends all peer nodes having bucket copies with searchable event counts less than the searchable event count of the canonical bucket copy an instruction to discard their respective bucket copies. The cluster manager sends the peer node storing the canonical bucket copy an instruction to replicate the canonical bucket copy to the peer nodes with discarded bucket copies.

## Claims

### Claim 1

A computer-implemented method, comprising:
performing a bucket recovery operation, comprising:
sending a request to a peer node to report a bucket health metric for a bucket copy corresponding to a corrupted bucket stored on the peer node,
obtaining, from a plurality of peer nodes, a corresponding bucket health metric comprising a searchable event count of the respective bucket copy stored on the peer node, and
electing, as a canonical bucket copy, a bucket copy having a searchable event count with a highest value, wherein the canonical bucket copy is stored on an elected peer node.

### Claim 2 (depends on 1)

The method of claim 1, wherein the plurality of peer nodes includes peer nodes that store the bucket copy corresponding to the corrupted bucket.

### Claim 3 (depends on 1)

The method of claim 1, wherein
the request to report the bucket health metric is received by a first peer node of the plurality of peer nodes; and
wherein the method further comprises rebuilding, by the first peer node, the bucket copy stored on the first peer node responsive to the request.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
reporting, by a first peer node of the plurality of peer nodes, to a cluster manager, a bucket rebuild process status of the first peer node and an updated bucket health metric of the bucket copy stored on the first peer node,
wherein the updated bucket health metric includes at least the searchable event count.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
by a cluster manager, prior to sending a replicate command to the elected peer node storing the canonical bucket copy to replicate the canonical bucket copy to at least a portion of the plurality of peer nodes,
sending an instruction to a first peer node of the plurality of peer nodes to discard the respective bucket copy stored on the first peer node,
wherein the searchable event count corresponding to the respective bucket copy stored on the first peer node is less than the searchable event count corresponding to the canonical bucket copy.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
adding, by a cluster manager, an identifier of the corrupted bucket to a corrupted bucket queue, wherein the corrupted bucket queue comprises a plurality of identifiers corresponding to a plurality of corrupted buckets.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
scheduling, by a cluster manager, a plurality of concurrent instances of a bucket recovery process for each corrupted bucket of at least a subset of the plurality of identifiers in a corrupted bucket queue,
wherein the plurality of concurrent instances of the bucket recovery process is less than a concurrent instance threshold.

### Claim 8 (depends on 1)

The method of claim 1, wherein the plurality of peer nodes stores a plurality of machine generated events in a plurality of buckets, the plurality of buckets comprising the corrupted bucket; and wherein a number of bucket copies corresponding to the corrupted bucket corresponds to a replication factor.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
receiving, by a cluster manager, a notification of the corrupted bucket from an administrative application, as at least one of a representational state transfer (REST) call, a command line instruction (CLI), and a Web User Interface (WebUI) call.

### Claim 10 (depends on 1)

The method of claim 1, further comprising receiving a notification of the corrupted bucket from a first peer node of a peer cluster.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
generating, by a first peer node, a read error notification; and
adding, by a peer engine executing on the first peer node, an identifier of the corrupted bucket to a corrupted bucket queue corresponding to the first peer node, wherein the corrupted bucket queue corresponding to the first peer node comprises a plurality of identifiers of a plurality of corrupted buckets.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
periodically sending, by a first peer node, a corrupted bucket queue as a notification to a cluster manager by a REST Hypertext Transfer Protocol (HTTP) request.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
determining, by a first peer node, during a restart process, a mismatch between a first bucket journal size corresponding to a first bucket health metric of a bucket of the first peer node and a second bucket journal size stored in a bucket manifest entry corresponding to the bucket from a bucket manifest stored on the first peer node, and transmitting, by the first peer node, a notification responsive to the mismatch.

### Claim 14

A computing device, comprising:
a processor; and
a non-transitory computer-readable medium having stored thereon instructions that, when executed by the processor, cause the processor to perform operations comprising:
performing a bucket recovery operation, comprising:
sending a request to a peer node to report a bucket health metric for a bucket copy corresponding to a corrupted bucket stored on the peer node,
obtaining, from a plurality of peer nodes, a corresponding bucket health metric comprising a searchable event count of the respective bucket copy stored on the peer node, and
electing, as a canonical bucket copy, a bucket copy having a searchable event count with a highest value, wherein the canonical bucket copy is stored on an elected peer node.

### Claim 15 (depends on 14)

The computing device of claim 14, wherein the plurality of peer nodes includes peer nodes that store the bucket copy corresponding to the corrupted bucket.

### Claim 16 (depends on 14)

The computing device of claim 14, wherein
the request to report the bucket health metric is received by a first peer node of the plurality of peer nodes; and
wherein the operations further comprise rebuilding, by the first peer node, the bucket copy stored on the first peer node responsive to the request.

### Claim 17 (depends on 14)

The computing device of claim 14, wherein the operations further comprise:
reporting, by a first peer node of the plurality of peer nodes, to a cluster manager, a bucket rebuild process status of the first peer node and an updated bucket health metric of the bucket copy stored on the first peer node,
wherein the updated bucket health metric includes at least the searchable event count.

### Claim 18 (depends on 14)

The computing device of claim 14, wherein the plurality of peer nodes stores a plurality of machine generated events in a plurality of buckets, the plurality of buckets comprising the corrupted bucket; and wherein a number of bucket copies corresponding to the corrupted bucket corresponds to a replication factor.

### Claim 19

A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
performing a bucket recovery operation, comprising:
sending a request to a peer node to report a bucket health metric for a bucket copy corresponding to a corrupted bucket stored on the peer node,
obtaining, from a plurality of peer nodes, a corresponding bucket health metric comprising a searchable event count of the respective bucket copy stored on the peer node, and
electing, as a canonical bucket copy, a bucket copy having a searchable event count with a highest value, wherein the canonical bucket copy is stored on an elected peer node.

### Claim 20 (depends on 19)

The non-transitory computer-readable medium of claim 19, wherein the plurality of peer nodes includes peer nodes that store the bucket copy corresponding to the corrupted bucket.
