Self-Contained Disaster Detection in Replicated Multi-Controller Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed computing systems face challenges in accurately determining site failures, leading to unnecessary resource usage and disruptions during disaster recovery procedures, as conventional methods are prone to false positives and external intervention delays.
Innovation Solution
Implementing a self-contained system with a data synchronization component, status monitoring component, and disaster recovery component that replicate and monitor status identifiers within a distributed computing system, allowing sites to independently detect and respond to failures without external intervention, thereby reducing false positives and improving response speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional disaster detection methods are used, then system simplicity is maintained, but false positives increase and response accuracy deteriorates
Solution Approach 1:
The replicated site performs self-contained disaster detection by monitoring status identifiers in replicated data without requiring external intervention. The system uses its own replicated data to detect failures at the primary site, eliminating dependency on external monitoring systems and reducing false positives while maintaining accuracy.
Solution Approach 2:
The system creates a copy of the primary site's data and status identifiers at the replicated site. By monitoring the status identifiers in this copy, the replicated site can detect failures at the primary site without direct communication, enabling accurate disaster detection while avoiding the complexity of external monitoring infrastructure.
2Productivity
If external intervention is required for disaster detection, then system complexity is reduced, but response time increases and productivity decreases
Solution Approach 1:
The replicated site autonomously detects disasters by monitoring status identifiers in its locally cached replicated data. This self-service approach eliminates the need for external intervention, significantly reducing response time while the distributed nature of the system keeps the added complexity manageable across multiple sites.
Solution Approach 2:
The system performs preliminary actions by continuously replicating data and maintaining status identifiers at the replicated site before failures occur. This pre-positioned data enables immediate local detection and response when failures happen, eliminating delays associated with external monitoring and intervention.
3Reliability
If unnecessary recovery procedures are executed, then system reliability is improved through frequent checks, but resource usage increases and energy consumption worsens
Solution Approach 1:
The system replaces mechanical/discrete recovery procedures with a more efficient monitoring approach based on status identifier changes in replicated data. By detecting actual failures through status identifier monitoring rather than relying on timed recovery cycles, the system maintains reliability while reducing unnecessary resource consumption.
Solution Approach 2:
The system uses feedback from status identifier monitoring in replicated data to trigger recovery procedures only when actual failures are detected. This feedback mechanism ensures that recovery procedures are executed only when necessary, maintaining system reliability while avoiding the resource waste associated with frequent unnecessary recovery attempts.
Data Source
AI summary
Self-contained disaster detection for replicated multi-controller systems is described herein. A system as described herein can include a memory that stores computer executable components and a processor that executes computer executable components stored in the memory. The computer executable components can include a data synchronization component that replicates data written at a primary production site, resulting in replicated data from the primary production site; a status monitoring component that reads status identifiers contained in the replicated data at periods of a time interval, wherein the status identifiers are written by respective controllers at the primary production site; and a disaster recovery component that initializes a failover procedure at the primary production site in response to an absence of updates to a first threshold number of the status identifiers within a second threshold number of the periods.