Failover
The automatic process of switching incoming traffic from a failed primary server, data centre, or service instance to a healthy standby or backup. Failover is triggered by health check failures — when a backend stops responding to health probes within a configured timeout and retry count, the load balancer removes it from the active pool and redistributes its connections. Active-active configurations handle failure by rebalancing across remaining healthy nodes; active-passive configurations promote a standby node. DNS-based failover at the GSLB level redirects entire regions. Recovery and fail-back policies determine when a recovered server re-enters the active pool.
البروتوكولات ذات الصلة
مذكور في الأدلة
DNS TTL: How to Set TTL Values and Avoid Propagation Delays
DNS & Networking
DNS-Based Failover and High Availability
DNS & Networking
Load Balancer Health Checks: HTTP, TCP, and gRPC Probes
Production Infrastructure
CDN Configuration for Dynamic and Static Content
Production Infrastructure
API Gateway Patterns: Architecture and Use Cases
API Gateway Patterns