17887010. AUTOMATED REGIONAL FAILOVER simplified abstract (Capital One Services, LLC)
Contents
AUTOMATED REGIONAL FAILOVER
Organization Name
Inventor(s)
Ateet Kumar Awasthi of Mckinney TX (US)
Chris Fields of Roanoke TX (US)
Saral Jain of Mckinney TX (US)
Matt Howarth of Garland TX (US)
AUTOMATED REGIONAL FAILOVER - A simplified explanation of the abstract
This abstract first appeared for US patent application 17887010 titled 'AUTOMATED REGIONAL FAILOVER
Simplified Explanation
- System, method, and computer program product for automatically failing over services from a primary region to a secondary region upon detection of a fault. - Method involves preparing an input file with a list of service names operating on the primary region, then modifying service weights to fail over each service to the secondary region. - Can also fail over databases corresponding to the failed-over services simultaneously. - Introduces a sleep time after modifying each service weight to prevent potential throttling issues.
Potential Applications
- Cloud computing - Disaster recovery systems - High availability systems
Problems Solved
- Ensures continuous operation of services in case of a fault in the primary region - Minimizes downtime and service disruptions
Benefits
- Automatic failover process reduces manual intervention - Improves system reliability and availability - Enhances overall system performance and resilience
Original Abstract Submitted
Disclosed herein are system, method, and computer program product embodiments for automatically failing over all services operating on a primary region to a secondary region upon detection or notification of a fault in the primary region. When a fault exists on the primary region, the method traverses each cluster containing services operating on the primary region and prepares an input file including a list of service names identifying each service operating on the primary region. Referencing the input file, the method fails over each service from the primary region to the secondary region by modifying a service weight corresponding to each service. This failover process of services may be done simultaneously with failing over any databases corresponding to the failed-over services from the primary region to the secondary region. The method may also introduce a sleep time after modifying each service weight to avoid any potential throttling issues.
