WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.
Configuring Lustre for Failover: Difference between revisions
From Obsolete Lustre Wiki
Jump to navigationJump to search
(Created page with 'If you plan to enable failover server functionality with Lustre (either on an OSS or MDS), you must add high-availability (HA) software to your cluster software. You can use any ...') |
No edit summary |
||
| Line 1: | Line 1: | ||
If you plan to enable failover server functionality with Lustre (either on an OSS or MDS), you must add high-availability (HA) software to your cluster software. You can use any HA software package with Lustre. | If you plan to enable failover server functionality with Lustre (either on an OSS or MDS), you must add high-availability (HA) software to your cluster software. You can use any HA software package with Lustre. | ||
Heartbeat is one option that supports a redundant system with access to shared (common) storage with dedicated connectivity. Heartbeat can determine the system’s general state. For more information, see | Heartbeat is one option that supports a redundant system with access to shared (common) storage with dedicated connectivity. Heartbeat can determine the system’s general state. For more information, see Chapter 8:''Failover'' in the [[Lustre Documentation|''Lustre Operations Manual'']]. | ||
Revision as of 13:59, 30 October 2009
If you plan to enable failover server functionality with Lustre (either on an OSS or MDS), you must add high-availability (HA) software to your cluster software. You can use any HA software package with Lustre.
Heartbeat is one option that supports a redundant system with access to shared (common) storage with dedicated connectivity. Heartbeat can determine the system’s general state. For more information, see Chapter 8:Failover in the Lustre Operations Manual.
