Distributed Object Replication with Dynamic Worker Scaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data replication systems are unable to adapt to changing requirements, leading to inefficiencies such as over- or under-provisioning of resources, resulting in either wasteful resource allocation or unacceptably long replication times.

Innovation Solution

A distributed object replication system that dynamically allocates and deallocates worker nodes based on factors like bandwidth, IOPS, and computing costs, using a microservices architecture to efficiently replicate data across multiple sites, including both cloud and non-cloud environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If resources are over-provisioned to ensure replication completion, then replication speed is improved, but resource waste increases

Engineering Contradiction:
Improvereplication speedVSAvoidresource waste
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The system dynamically adjusts the number of worker nodes allocated to replication tasks based on real-time monitoring of replication progress, data volume, and resource availability. This allows the system to optimize replication speed while avoiding resource waste by provisioning only the necessary computational resources at any given moment rather than maintaining fixed over-provisioned capacity.

Inventive Principle:
Principle #15Dynamics

2Loss of energy

If resources are under-provisioned to reduce resource allocation, then resource efficiency is improved, but replication time becomes unacceptably long

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidreplication time
Core Design Contradiction:
Loss of energyVSDuration of action of moving object

Solution Approach 1:

The system continuously monitors replication task progress and dynamically scales worker node allocation upward when replication lag is detected or data volume increases, ensuring replication completes within acceptable timeframes while maintaining resource efficiency during periods of lower demand.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback loops that monitor replication task performance metrics and automatically adjust worker node provisioning based on observed replication speeds and remaining data volumes, allowing the system to adapt resource allocation to actual needs rather than relying on static estimates.

Inventive Principle:
Principle #23Feedback

3Device complexity

If fixed resource allocation is used to simplify system management, then system complexity is reduced, but adaptability to changing requirements deteriorates

Engineering Contradiction:
Improveresource management complexityVSAvoidadaptability to changing requirements
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system automatically monitors its own replication task requirements and adjusts worker node allocation without manual intervention, using embedded monitoring agents that track replication progress and trigger dynamic resource provisioning based on predefined performance thresholds and organizational policies.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If dynamic resource allocation is implemented to improve adaptability, then adaptability to changing requirements is improved, but system complexity increases

Engineering Contradiction:
Improveadaptability to changing requirementsVSAvoidresource management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces intermediary components including resource brokers, monitoring agents, and policy engines that mediate between replication task requirements and underlying computational resources, abstracting the complexity of dynamic resource allocation while enabling flexible adaptation to changing replication demands.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11010240B2Tracking status and restarting distributed replication
Publication Date: 2021.05.18 EMC IP HLDG CO LLC
  • US11010240B2 patent drawing
  • US11010240B2 patent drawing
  • US11010240B2 patent drawing

AI summary

A controller at a source site generates a set of tasks associated with a replication job. Each task includes one or more of copying an object from the source to destination site, or deleting an object from the destination site. The tasks are placed onto a message queue at the source site. Source worker nodes at the source site retrieve the tasks from the source site message queue for processing in conjunction with destination worker nodes at the destination site. A destination worker node, upon receiving a task from a source worker nodes, places the task onto a message queue at the destination site for retrieval by a backend worker node that handles writing to an object store at the destination site.