Delta File Distribution for Lookup Table Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern data centers face challenges in efficiently processing and indexing large volumes of machine-generated data due to the unstructured nature of the data, leading to inefficiencies in data updates and synchronization across multiple users and interfaces, resulting in undesirable delays and conflicts.

Innovation Solution

The method involves generating a delta file that identifies the divergence between current and previous reference data structures in a search head, distributing the delta file to indexers, and replicating it to other search heads, ensuring compatibility and reducing network bandwidth consumption by only transmitting updates, thereby maintaining data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire lookup tables are distributed to maintain data consistency across multiple users and interfaces, then data integrity is ensured, but network bandwidth consumption increases and synchronization delays occur

Engineering Contradiction:
Improvedata integrityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the changed portions (deltas) from the complete lookup table and distributes only these deltas to indexers. This is achieved by identifying modifications between the previous version of the lookup table and the current version, then transmitting only the divergent entries rather than the entire table, thereby reducing network bandwidth consumption while maintaining data consistency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the lookup table update process into identifying divergences between versions and transmitting only the changed segments (deltas). This segmentation allows the system to break down the large-scale data distribution problem into smaller, more efficient delta transmissions, reducing overall network bandwidth consumption while ensuring data integrity through version tracking.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire lookup tables are distributed to ensure data consistency, then data integrity is maintained, but synchronization delays and conflicts increase

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and transmits only the divergent portions (deltas) between lookup table versions rather than distributing entire tables. This extraction approach significantly reduces synchronization time and eliminates delays associated with transmitting redundant data, while maintaining data consistency through version identification and selective delta distribution.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the necessary portion of data (deltas) required to maintain consistency, rather than performing the excessive action of distributing complete lookup tables. This partial transmission approach reduces synchronization delays and conflicts while ensuring data integrity through targeted delta updates.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If lookup tables are frequently updated to reflect real-time data changes, then data currency is improved, but network bandwidth consumption and system complexity increase

Engineering Contradiction:
Improvedata currencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts only the changed entries (deltas) from lookup table updates and transmits these selectively to indexers. This approach maintains data currency by promptly distributing updates while minimizing network bandwidth consumption by avoiding transmission of unchanged data, thus resolving the contradiction between data freshness and bandwidth usage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the minimal necessary data (deltas) required to maintain data currency, rather than performing excessive full table distributions. This reduces network bandwidth consumption while maintaining real-time data accuracy through selective delta updates.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If entire lookup tables are distributed to maintain consistency, then data integrity is ensured, but device complexity and conflict potential increase

Engineering Contradiction:
Improvedata integrityVSAvoidsynchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and transmits only the divergent portions (deltas) between lookup table versions, reducing the complexity of synchronization operations. This extraction approach simplifies the distribution process while maintaining data integrity through version tracking and selective delta application at indexer locations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the lookup table into identifiable divergences between versions, allowing selective transmission and application of only the changed portions. This segmentation reduces synchronization complexity and conflict potential while maintaining data integrity through targeted delta updates rather than full table replacements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11809405B2Generating and distributing delta files associated with mutable events in a distributed system
Publication Date: 2023.11.07 CISCO TECHNOLOGY INC
  • US11809405B2 patent drawing
  • US11809405B2 patent drawing
  • US11809405B2 patent drawing

AI summary

The present disclosure provides solutions for determining the divergence (delta) between the current and previous reference data structures for mutable data in a search head. A method is provided that includes updating a pre-existing lookup table in a search head, generating a delta file that identifies the divergence between the updated and previous lookup table, and distributing the delta file to other components in the search environment. The compatibility of the delta file is checked with the local instance of the lookup table in each search component, and the lookup table is applied if compatibility is determined. However, if the delta file is determined to not be compatible with the current version of a local lookup table in an indexer, the entire lookup table sent to the requesting indexer instead.