Pro-active Self-Healing in Distributed File Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional self-healing solutions in distributed file systems rely on client devices to initiate the self-healing process, which consumes significant resources and delays file access until the healing is complete, causing performance issues and waiting times for client applications.

Innovation Solution

Implementing a pro-active self-healing module on storage server machines that detects a recovered server reconnecting to the cluster and automatically initiates the self-healing process without waiting for client application access, using a daemon that crawls the replication directory hierarchy to identify and update stale files with fresh data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional client-driven self-healing is used, then data consistency is maintained across the distributed file system, but client device performance deteriorates due to significant resource consumption and waiting times

Engineering Contradiction:
Improvedata consistencyVSAvoidclient device performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service by enabling storage server machines to autonomously detect their own failure state and initiate self-healing operations without requiring client device intervention. The storage server monitors its own health status, detects failures, and automatically triggers data recovery from replica copies, thereby maintaining data consistency while freeing client devices from resource-intensive self-healing operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent inverts the traditional self-healing architecture by shifting the initiative from client-driven to server-driven operations. Instead of clients detecting failures and triggering healing, storage servers autonomously detect their own failures and initiate healing processes. This inversion transfers the computational burden from clients to servers, improving client performance while maintaining data consistency through automated server-side healing.

Inventive Principle:
Principle #13The other way round (Inversion)

2Reliability

If traditional client-driven self-healing is used, then data consistency is maintained, but file access time increases due to waiting for healing completion

Engineering Contradiction:
Improvedata consistencyVSAvoidfile access time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by implementing proactive monitoring and early detection of storage server failures. The system continuously monitors server health status and initiates self-healing operations immediately upon detecting a failure, before client applications attempt to access affected files. This preliminary detection and immediate response minimizes the time files remain inaccessible, reducing file access delays while maintaining data consistency through automated healing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

By enabling storage servers to autonomously detect failures and initiate healing without client intervention, the system eliminates the waiting period where clients must poll or wait for healing completion. Servers perform self-service healing in the background, allowing clients to access files immediately after failure detection without timing out or waiting for explicit healing confirmation, thus reducing file access time while maintaining consistency.

Inventive Principle:
Principle #25Self-service

3Reliability

If traditional self-healing solutions are used, then data recovery is achieved, but significant client device resources are consumed

Engineering Contradiction:
Improvedata recoveryVSAvoidclient device resource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements self-service by transferring the resource-intensive self-healing operations from client devices to storage server machines. Storage servers autonomously monitor their own health status, detect failures, and execute data recovery operations using their own computational resources. This eliminates the need for client devices to consume significant resources for failure detection and healing initiation, while still achieving complete data recovery through automated server-side operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent extracts the self-healing functionality from the client device and relocates it to the storage server machine. By separating the failure detection and healing initiation functions from the client, the system removes the resource burden from client devices. The storage server independently performs monitoring, failure detection, and healing operations, achieving data recovery without requiring client device resources for these operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9529817B2Pro-active self-healing in a distributed file system
Publication Date: 2016.12.27 RED HAT INC
  • US9529817B2 patent drawing
  • US9529817B2 patent drawing
  • US9529817B2 patent drawing

AI summary

Techniques for pro-active self-healing in a distributed file system are disclosure herein. In accordance with one embodiment, a method is provided. The method comprises prior to detecting an access request by a client application to an image on a storage server, identifying, by a self-healing daemon executed by a processing device, a first region of the image comprising stale data. A partial lock on the image is acquired. The partial lock prevents access to the first region of the image. Responsive to acquiring the partial lock, the self-healing daemon provides access to a second region of the image file comprising data other than the stale data.