Search Head Cluster Journal Replication for Configuration Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern data centers face challenges in consistently replicating user-defined configuration customizations across multiple search heads to ensure a uniform user experience, particularly due to the unstructured nature of machine-generated data and the complexity of indexing and searching operations.

Innovation Solution

A system is implemented where search heads in a cluster operate as a hub-spoke arrangement, with one designated leader responsible for synchronizing knowledge object customizations across all search heads, using a journal and configuration file to record and replicate changes, ensuring eventual consistency and a consistent configuration across the cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If configuration customizations are allowed to be modified individually at each search head, then local flexibility and adaptability are improved, but configuration consistency and uniformity across the cluster deteriorate

Engineering Contradiction:
Improvelocal configuration flexibilityVSAvoidconfiguration consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The configuration management system is segmented into multiple search heads, each capable of independent configuration modifications. This segmentation allows local flexibility while the overall system maintains consistency through the journal replication mechanism that distributes changes across all segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The journal acts as a feedback mechanism that tracks configuration changes at each search head and propagates these changes to other search heads. This feedback loop ensures that local modifications are communicated back to the cluster, maintaining configuration consistency across all nodes.

Inventive Principle:
Principle #23Feedback

2Stability of the object's composition

If configuration changes are replicated across all search heads, then configuration consistency is improved, but system complexity and synchronization overhead increase

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The journal serves as an intermediary mechanism that simplifies the replication process. Instead of direct peer-to-peer synchronization between search heads, the journal acts as a mediator that receives, records, and distributes configuration changes, reducing the complexity of the synchronization mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Configuration changes are copied from the journal to each search head's configuration files. This copying mechanism ensures consistency across the cluster while keeping the synchronization process simple and straightforward, avoiding complex real-time coordination protocols.

Inventive Principle:
Principle #26Copying

3Stability of the object's composition

If journal entries are replicated to all search heads, then configuration uniformity is improved, but data transmission volume and processing time increase

Engineering Contradiction:
Improveconfiguration uniformityVSAvoiddata transmission volume
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

Only the necessary configuration change information is extracted and replicated from the journal to search heads, rather than transmitting entire configuration files or redundant data. This extraction approach reduces the volume of data transmitted while maintaining configuration uniformity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Configuration changes are recorded in the journal before being replicated to other search heads. This preliminary action allows the system to prepare and validate changes locally, reducing the need for repeated transmissions and minimizing overall data volume exchanged across the network.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11669499B2Management of journal entries associated with customizations of knowledge objects in a search head cluster
Publication Date: 2023.06.06 CISCO TECHNOLOGY INC
  • US11669499B2 patent drawing
  • US11669499B2 patent drawing
  • US11669499B2 patent drawing

AI summary

Replication of search-related configuration customizations across multiple individual configuration files of search heads of a cluster for a consistent user experience. A search head leader of the cluster can receive a first journal entry relating to a first customization of a knowledge object from a first search head of the cluster. The search head leader may determine that the first journal entry references a parent commit journal entry matching a latest commit journal entry in a journal maintained by the search head leader. The first journal entry can be stored in the journal and sent to one or more search heads of the cluster.