Volume Replica Migration for Storage Capacity Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Maintaining the availability and performance of computing resources in distributed systems, such as block-level data storage services, becomes challenging as the number of volumes grows, especially when servers reach capacity or require maintenance, leading to potential data unavailability and increased latency.

Innovation Solution

A movement system that dynamically migrates and reassigns data storage volumes based on usage data and customer profiles, creating new replicas, flipping master and slave replicas, and migrating data to new volumes to ensure continued availability and performance without impacting read/write operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If computing resources are maintained to service growing volumes, then service capacity is improved, but resource expense and overhead increase

Engineering Contradiction:
Improveservice capacityVSAvoidresource expense
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system dynamically migrates volume replicas between servers based on real-time capacity metrics and usage patterns. Servers can transition from active service to maintenance mode and back, with replicas being moved seamlessly to maintain service continuity while optimizing resource utilization across the distributed system

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system creates and manages replica copies of volume data across multiple servers. These replicas enable load balancing and failover capabilities, allowing the system to service more volumes without proportionally increasing primary storage resources, as replicas can be activated based on demand

Inventive Principle:
Principle #26Copying

2Reliability

If computing resources are maintained to ensure volume availability, then reliability is improved, but system complexity increases

Engineering Contradiction:
Improvevolume availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The movement system automatically monitors server capacity metrics, identifies migration opportunities, executes replica transfers, and updates system state without manual intervention. This self-managing capability maintains volume availability during server maintenance while avoiding the operational complexity of manual replica management

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors server capacity usage and performance metrics, using this feedback to dynamically adjust replica placement decisions. This closed-loop control ensures volume availability is maintained while automatically optimizing resource distribution, reducing the need for complex manual provisioning

Inventive Principle:
Principle #23Feedback

3Productivity

If data is migrated between replicas, then resource allocation is optimized, but data unavailability and latency may occur

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoiddata unavailability
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary capacity assessment and identifies migration targets before initiating data transfer. By pre-planning migrations during low-utilization periods and maintaining ready-state replicas, the system can execute migrations with minimal impact on data availability, as the groundwork is already prepared

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The movement system acts as an intermediary layer between storage clients and physical servers, abstracting the migration process from end users. During migration, this intermediary layer redirects access to alternative replicas or maintains access paths, ensuring data availability is preserved while the physical data moves between servers

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10656869B1Performance-based volume replica migration
Publication Date: 2020.05.19 AMAZON TECH INC
  • US10656869B1 patent drawing
  • US10656869B1 patent drawing
  • US10656869B1 patent drawing

AI summary

A movement system of a block-level data storage service obtains usage information for a data storage volume. The movement system processes the usage information to identify a placement strategy for the data storage volume that is associated with a second operational state for the data storage volume. Based on the placement strategy, the movement system causes a set of servers to perform an operation to implement the second operational state for the data storage volume. As a result of the operation being successfully performed, the movement system provides access to the data storage volume in accordance with the second operational state.