Live-Migration Protocol for Distributed Application Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for managing multiple applications on a cluster of servers fail to effectively address redundancy and load-balancing issues in high-latency networked systems, as they either incur high costs, impose performance overhead, or are limited by geographical constraints and the risk of data corruption.
Innovation Solution
A server configured to operate in either a master or slave role, with logic for replicating data across a cluster, autonomously switching roles based on events such as failure or load changes, using snapshot replication and heartbeats to maintain data consistency and balance load across servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtualisation is used to replicate every change in memory and system state to a second physical host, then application recovery capability is improved, but system cost and resource requirements worsen
Solution Approach 1:
The patent uses selective copying of only changed data blocks (incremental replication) rather than copying entire system states. The master server identifies and replicates only the differences between snapshot versions, significantly reducing network bandwidth and storage requirements while maintaining recovery capability.
Solution Approach 2:
The system pre-establishes replica servers in advance that can immediately take over if the master fails. These replicas maintain synchronized data through continuous incremental replication, so when failure occurs, failover is immediate without requiring complex real-time coordination or resource allocation during the failure event.
2Productivity
If manual moving of applications between servers is implemented, then load balancing capability is improved, but recovery time worsens
Solution Approach 1:
The system implements automated load balancing through heartbeat monitoring and autonomous failover logic. When the master server fails to send heartbeats, replica servers automatically detect the failure and promote themselves to master status without human intervention, eliminating manual recovery time while maintaining load balancing capabilities.
Solution Approach 2:
The master server continuously sends heartbeat signals to replicas, creating a feedback mechanism that allows the system to detect failures immediately. This real-time feedback enables automatic trigger of failover procedures, reducing recovery time from manual intervention delays to near-instantaneous automated response.
3Reliability
If shared storage backend is used in classical cluster, then application availability is improved, but system cost and single point of failure risk worsen
Solution Approach 1:
The patent segments the storage system into distributed local storage on each server rather than centralized shared storage. Each server maintains its own data blocks and replica servers store copies locally, eliminating the shared storage bottleneck and single point of failure while maintaining high availability through distributed redundancy.
Solution Approach 2:
The system introduces incremental replication as an intermediary mechanism between master and replicas, replacing the need for direct shared storage access. Instead of all servers competing for shared storage resources, data flows through controlled replication channels, eliminating the shared storage single point of failure while maintaining data consistency.
4Manufacturing precision
If synchronous replication is used across geographically diverse regions, then data consistency is improved, but network latency and system performance worsen
Solution Approach 1:
The system uses periodic incremental replication where replicas are updated at scheduled intervals based on change detection rather than continuously synchronizing every change immediately. This periodic update approach reduces network traffic intensity and latency impact while maintaining data consistency across geographic regions through regular synchronization cycles.
Solution Approach 2:
The patent implements partial replication by sending only the changed portions of data (incremental blocks) rather than complete data sets. This partial action approach reduces the volume of network traffic required for replication, thereby reducing latency and performance impact while still achieving data consistency across distributed regions.
Data Source
AI summary
A method and apparatus for distribution of applications amongst a number of servers, ensuring that changes to application data on a master for that application are asynchronously replicated to a number of slaves for that application. Servers may be located in geographically diverse locations; the invention permits data replication over high-latency and lossy network connections and failure-tolerance under hardware and network failure conditions. Access to applications is mediated by a distributed protocol handler which allows any request for any application to be addressed to any server, and which, when working in tandem with the replication system, pauses connections momentarily to allow seamless, consistent live-migration of applications and their state between servers. Additionally, a system which controls the aforementioned live-migration based on dynamic measurement of load generated by each application and the topological preferences of each application, in order to automatically keep servers at an optimum utilization level.