Index splitting in distributed databases
US12321327B2 · kind B2 · utility
Assignee
Inventor
Key dates
| Filing date | Jan 10, 2023 |
| Grant date | Jun 3, 2025 |
| Priority date | — |
| Expiry date | Jan 10, 2043 |
Classification
- Technology area (CPC H)Electricity
- CPC primaryH04L9/085
- WIPO fieldComputer technology
- WIPO sectorElectrical engineering
Abstract
In a distributed database, many nodes can store copies, or instances, of the same record. If the record is split on one node, it should be split on the other nodes to maintain consistency, concurrency, and correctness of the data in the distributed database. In some distributed databases, the records are locked during the update process to ensure data integrity. Unfortunately, locking the records can increase latency, especially for larger databases. But if the records aren't locked and a node fails as a record is being split and updated simultaneously, the split and update may not propagate throughout the distributed database, leading to a loss of data integrity. Exchanging messages about the status of record splitting and forwarding updates internally reduces the likelihood of a loss of data integrity due to a node failure.
Source: USPTO / EPO open patent data. Objective bibliographic and citation counts.