Write-Back Caching in Distributed Storage Nodes with Backup Power

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed storage systems often disable write-back caching due to the presence of nodes without backup power supplies, preventing performance benefits and risking data loss, even though nodes with backup power supplies could safely implement this caching method.

Innovation Solution

Identify storage nodes with backup power supplies, enable write-back caching on these nodes, and group them into a node pool to service write requests, ensuring that only nodes with backup power supplies perform caching, thereby minimizing data loss and enhancing performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If write-back caching is enabled on all storage nodes, then system performance is improved, but data loss risk increases due to nodes without backup power supplies

Engineering Contradiction:
Improvesystem performanceVSAvoiddata loss risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by enabling write-back caching only on storage nodes that have backup power supplies, rather than uniformly across all nodes. This allows each node to have different caching capabilities based on its power supply status, resolving the contradiction between performance improvement and data loss risk.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the storage system into two groups: nodes with backup power supplies and nodes without. This segmentation allows write-back caching to be selectively enabled on the appropriate subset of nodes, achieving performance benefits while maintaining data safety.

Inventive Principle:
Principle #1Segmentation

2Reliability

If write-back caching is disabled on nodes without backup power supplies, then data loss risk is reduced, but system performance deteriorates

Engineering Contradiction:
Improvedata loss preventionVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent enables write-back caching only on nodes with backup power supplies while disabling it on nodes without backup power supplies. This local differentiation resolves the contradiction by allowing performance optimization where safe and maintaining data protection where necessary.

Inventive Principle:
Principle #3Local quality

3Reliability

If the distributed storage system operates on the lowest common denominator, then system reliability is maintained, but functionality is limited

Engineering Contradiction:
Improvesystem reliabilityVSAvoidfunctionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent allows different functionality levels across different nodes based on their capabilities. Nodes with backup power supplies can provide write-back caching functionality, while nodes without backup power supplies operate without this feature. This resolves the contradiction between maintaining system reliability and enabling advanced functionality.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11397678B2Pooling distributed storage nodes that have backup power supplies and write-back caching capabilities
Publication Date: 2022.07.26 RED HAT INC
  • US11397678B2 patent drawing
  • US11397678B2 patent drawing
  • US11397678B2 patent drawing

AI summary

Distributed storage nodes having backup power supplies and write-back caching capabilities can be pooled for servicing write requests. For example, a management node of a distributed storage system can determine a subset of storage nodes, from among a group of storage nodes of the distributed storage system, coupled to backup power supplies based on status information received from the group of storage nodes. The status information can indicate whether a respective storage node of the group of storage nodes is coupled to a corresponding backup power supply. The management node can then generate a node pool that includes the subset of storage nodes with write-back caching enabled. The node pool can be configured to perform write-back caching in relation to a write request.