Database Rebalancing via Partial Node Set Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database rebalancing in storage systems with multiple nodes often leads to temporary performance degradation due to excessive data replication traffic, affecting overall system performance and application services.
Innovation Solution
A method involving partial rebalancing between subsets of database nodes, where some nodes continue to operate normally while others perform rebalancing, maintaining replication factors and minimizing performance degradation by distributing data and load across nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If full database rebalancing is performed simultaneously across all nodes, then data distribution uniformity is improved, but system performance deteriorates due to explosive replication traffic
Solution Approach 1:
The patent divides the database nodes into multiple node sets and performs rebalancing in sequential batches rather than simultaneously. Each node set is rebalanced independently while other sets continue normal operations, segmenting the rebalancing process to avoid explosive traffic while achieving progressive data distribution uniformity across the entire system.
Solution Approach 2:
The patent applies partial rebalancing by selecting only specific node sets for rebalancing at each step while leaving other node sets operational. This partial action approach allows the system to make progress toward uniform data distribution without requiring all nodes to participate simultaneously, thereby maintaining acceptable system performance.
2Speed
If all DB nodes participate in rebalancing simultaneously, then rebalancing speed is improved, but performance degradation increases
Solution Approach 1:
The patent segments the DB nodes into multiple node sets and performs rebalancing on one set at a time while others remain operational. This segmentation enables the system to maintain service continuity (improving reliability) while still achieving rebalancing progress through sequential processing of different node sets.
Solution Approach 2:
The patent ensures continuous service by allowing node sets not currently undergoing rebalancing to continue processing read and write requests normally. This continuity of useful action maintains system reliability while rebalancing progresses sequentially across different node sets.
3Reliability
If sequential partial rebalancing is performed across multiple node sets, then performance degradation is minimized, but rebalancing time increases
Solution Approach 1:
The patent segments the rebalancing process into multiple sequential node sets, where each set is rebalanced independently while others remain operational. This segmentation minimizes performance degradation at any given time but extends the total rebalancing duration as each segment must be processed sequentially.
Solution Approach 2:
The patent implements periodic rebalancing cycles where different node sets are selected for rebalancing in alternating periods. This periodic action allows the system to maintain stable performance during each cycle while progressively completing the overall rebalancing task through repeated cycles.
Data Source
AI summary
Provided are a database rebalancing method including three or more database (DB) nodes, the method comprises configuring a first node set including two or more DB nodes from among the three or more DB nodes included in the storage system, performing a first partial rebalancing between DB nodes of the first node set, during the first partial rebalancing, performing a first partial rebalancing cover step in which DB nodes excluded from the first node set perform a normal operation, configuring a second node set including two or more DB nodes from among the three or more DB nodes included in the storage system, performing a second partial rebalancing between DB nodes of the second node set, the second partial rebalancing being performed after completion of the first partial rebalancing and during execution of the second partial rebalancing, performing a second partial rebalancing cover step in DB nodes excluded from the second node set perform a normal operation, wherein at least one DB node included in the first node set is not included in the second node set, or at least one DB node included in the second node set is not included in the first node set.