Differences
This shows you the differences between two versions of the page.
| — | high_availability [2015/06/01 22:29] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== High Availability ====== | ||
| + | * [[CDN]] | ||
| + | * [[haproxy]] - HTTP proxy | ||
| + | * [[heartbeat]] | ||
| + | * [[Load Balancing]] | ||
| + | * [[mysql-proxy]] | ||
| + | * [[monit]] | ||
| + | * [[squid]] | ||
| + | |||
| + | == About == | ||
| + | |||
| + | High Availability involves doing everything possible to keep a server self-maintained, | ||
| + | |||
| + | == Planning == | ||
| + | |||
| + | First, consider the reasons that a server or service could become unavailable. | ||
| + | |||
| + | Causes for service unavailability can be hedged by software solutions that do two jobs: monitor and repair any damage possible, and alert the administrators of possible issues that require personal attention. | ||
| + | |||
| + | == Prevention == | ||
| + | |||
| + | The best way to prevent outages is to gauge the expected server load, and configure the services to operate within parameters that will not exceed the available resources. | ||
| + | |||
| + | == Accessibility == | ||
| + | |||
| + | Granting access to a system | ||
| + | |||
| + | == Goals == | ||
| + | |||
| + | * Keep a system online | ||
| + | * Keep all services active | ||
| + | * Remote access available | ||
| + | * Warn systems admin about possible issues | ||
| + | * Reduce single points of failure | ||
| + | |||
| + | == Methodologies == | ||
| + | |||
| + | * Monit - manage services | ||
| + | * collectd - gather system statistics | ||
| + | * High availability proxies - round-robin of servers | ||
| + | * Database clusters | ||
