Buddy Replication for Cache Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing clustered tree-structured caches face challenges in managing replication efficiently, leading to increased memory usage and network traffic as the number of nodes in the cluster grows, which can impact performance and scalability.

Innovation Solution

The implementation of buddy replication, where data is replicated to a finite number of designated nodes rather than the entire cluster, along with the use of asynchronous replication and transactional boundaries to minimize traffic and ensure data consistency, and the configuration of buddy replication settings through XML elements to manage cluster behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated to all instances in the cache cluster, then data redundancy and security are improved, but memory usage and network traffic increase significantly

Engineering Contradiction:
Improvedata redundancyVSAvoidmemory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent divides the cache cluster into primary instances and secondary instances. Data is segmented such that primary instances hold the original data while secondary instances hold replicated copies. This segmentation allows replication without requiring every instance to store every piece of data, thus reducing overall memory usage while maintaining redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to replication by distinguishing between primary and secondary instances. Instead of flat replication to all nodes, the system creates a two-level structure where data flows from primary to secondary instances. This dimensional change enables controlled replication that reduces memory overhead while preserving data availability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If data is replicated to all instances in the cache cluster, then data redundancy and security are improved, but network traffic increases significantly

Engineering Contradiction:
Improvedata redundancyVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the replication function from a universal all-to-all model and confines it to specific primary-secondary instance pairs. By taking out the unnecessary replication paths, the system reduces network traffic while maintaining the essential redundancy function. Only critical replication routes are activated.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The network communication is segmented into specific primary-to-secondary transmission paths rather than broadcast to all instances. This segmentation of communication channels reduces overall network traffic while ensuring data reaches the necessary secondary instances for redundancy.

Inventive Principle:
Principle #1Segmentation

3Reliability

If replication is performed every time another instance is added to the cluster, then data consistency is maintained, but performance and scalability are impacted

Engineering Contradiction:
Improvedata consistencyVSAvoidscalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic replication where the system adapts replication behavior based on cluster conditions. When instances are added, the system dynamically determines which secondary instances need data rather than forcing universal replication. This dynamic approach maintains consistency while improving scalability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of replication frequency and scope based on cluster events. Instead of always replicating on every instance addition, the system adjusts replication parameters to replicate only when necessary, balancing data consistency with performance and scalability requirements.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8762664B2Replicating cache nodes in a cluster
Publication Date: 2014.06.24 RED HAT INC
  • US8762664B2 patent drawing
  • US8762664B2 patent drawing
  • US8762664B2 patent drawing

AI summary

A method and apparatus for replicating instances of cache nodes in a cluster is described. In one embodiment, the number of available cache nodes in the cluster is determined. Available cache nodes from the cluster are selected based on a parameter. An instance of a cache node is replicated to only one of the selected cache nodes in the cluster.