Erasure-Coded Fragment Pulling for Overloaded Server Replacement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Load balancing in distributed content delivery systems is complex due to the need for inter-server synchronization, especially when dealing with redundant data, and existing methods struggle to efficiently manage server loads and failures without significant coordination.
Innovation Solution
A method involving fractional-storage servers that use an erasure-coded fragment pull protocol to identify and replace loaded servers with underloaded ones, ensuring continuous delivery of erasure-coded fragments and maintaining load balance without extensive inter-server coordination, utilizing a fragment pull protocol to retrieve and replace servers dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If inter-server synchronization is implemented to balance load in distributed systems, then load balancing capability is improved, but system complexity and coordination overhead increase
Solution Approach 1:
Each server independently monitors its own load conditions and autonomously decides when to transfer fragments to other servers based on pre-established erasure coding relationships, without requiring complex centralized coordination or inter-server synchronization protocols
Solution Approach 2:
Erasure coding is performed in advance to create redundant fragment relationships between servers before load balancing is needed. This preliminary encoding establishes predetermined transfer paths and relationships, eliminating the need for real-time coordination when load balancing occurs
2Ease of operation
If redundant data is increased to facilitate load balancing, then load balancing ease is improved, but storage requirements and data management complexity increase
Solution Approach 1:
The redundancy factor in erasure coding is made dynamic and adjustable. System administrators can configure the level of redundancy based on specific load balancing requirements, allowing optimization between storage overhead and load balancing capability. The coding parameters can be changed without redesigning the entire system
3Productivity
If server replacement is performed to balance load, then system throughput is maintained, but replacement complexity and potential service disruption increase
Solution Approach 1:
When a server needs to be replaced or removed from the system, its erasure-coded fragments are copied to other available servers that have corresponding encoding relationships. This copying mechanism allows seamless replacement without requiring complex data migration or system reconfiguration
Solution Approach 2:
The erasure coding structure provides built-in redundancy that cushions against server failures or replacements. Before any replacement occurs, the redundant fragment relationships are already in place, ensuring that system throughput is maintained and no service disruption occurs during the replacement process
Data Source
AI summary
Load-balancing a distributed system by replacing overloaded servers, including the steps of retrieving, by an assembling device using a fragment pull protocol, erasure-coded fragments associated with segments, from a set of fractional-storage servers. Occasionally, while retrieving the fragments, identifying at least one server from the set that is loaded to a degree requiring replacement, and replacing, using the fragment pull protocol, the identified server with a substitute server that is not loaded to the degree requiring replacement. Wherein the substitute server and the remaining servers of the set are capable of delivering enough erasure-coded fragments in the course of reconstructing the segments.