Deduplication Filesystem Load Balancing for Service Overload Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing approaches to distributing network traffic across servers in a cluster with a distributed deduplicated filesystem do not account for the unique characteristics and challenges posed by such systems, leading to potential overloading of components and reduced performance.

Innovation Solution

Implement a load-balancing technique that uses consistent hashing algorithms and multiple weights to redirect client requests to available access object services, considering compute resources and historical workload patterns to prevent overloading and ensure efficient distribution of data protection traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If typical load-balancing approaches are used to distribute network traffic across cluster servers, then traffic distribution is achieved, but access object services may become overloaded due to not accounting for deduplicated filesystem characteristics

Engineering Contradiction:
Improvetraffic distribution efficiencyVSAvoidservice overload prevention
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The load-balancing approach dynamically adjusts service selection based on real-time loading conditions. The system monitors current loading states of access object services and adapts routing decisions accordingly, rather than using static distribution methods. This allows the system to respond to changing workload conditions and prevent overload while maintaining efficient traffic distribution.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring loading conditions of access object services and using this information to make informed routing decisions. The load-balancing approach incorporates loading state information from the deduplicated filesystem services to dynamically adjust traffic distribution, ensuring that services are not overwhelmed while maintaining optimal performance.

Inventive Principle:
Principle #23Feedback

2Device complexity

If simple load distribution methods are applied, then implementation complexity is reduced, but performance optimization for deduplicated filesystem operations is lost

Engineering Contradiction:
Improveload-balancing implementation complexityVSAvoiddata protection traffic handling efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The load-balancing system performs preliminary assessment of service loading conditions before routing client requests. By evaluating the current state of access object services in advance and selecting appropriate services based on their loading conditions, the system optimizes traffic distribution without requiring complex real-time adjustments during request processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12524377B2Load-balancing data protection traffic
Publication Date: 2026.01.13 DELL PROD LP
  • US12524377B2 patent drawing
  • US12524377B2 patent drawing
  • US12524377B2 patent drawing

AI summary

A set of categories are associated to each service of a set of services of a deduplication filesystem hosted across a cluster of nodes. The categories describe loadings on the services. A preliminary identification of a service to which a client request should be redirected is made. Checks are made of the loadings on the service. The checking includes calculating thresholds for the categories, observing current values for the categories, comparing the current values against the thresholds, setting individual weights on the categories based on the comparison, and deriving a final weight for the service based on the individual weights. If the final weight indicates that the service is not overloaded, the request is redirected to the service. If the final weight indicates that the service is overloaded, the checking is iterated over a next service to find a service that is not overloaded.