From 756ce050e2891d730a0eb4f4a82cd220c3ae871b Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Mon, 16 May 2011 14:48:19 -0500 Subject: [PATCH] FIX: converted to chapter and removed cruft --- UnderstandingFailover.xml | 117 ++-------------------------------------------- 1 file changed, 3 insertions(+), 114 deletions(-) diff --git a/UnderstandingFailover.xml b/UnderstandingFailover.xml index e553e20..b148968 100644 --- a/UnderstandingFailover.xml +++ b/UnderstandingFailover.xml @@ -1,70 +1,8 @@ -
+ - + Understanding Failover in Lustre - - - - - - - - - Lustre 2.0 Operations Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - C H A P T E R  3 - - - - -   - - - - - - - Understanding Failover in Lustre - - - - This chapter describes failover in a Lustre system. It includes: What is Failover? @@ -241,56 +179,7 @@ In an active configuration, 50% of the available OSTs are assigned to one OSS and the remaining OSTs are assigned to the other OSS. Each OSS serves as the primary node for half the OSTs and as a failover node for the remaining OSTs. In this mode, if one OSS fails, the other OSS takes over all of the failed OSTs. The clients attempt to connect to each OSS serving the OST, until one of them responds. Data on the OST is written synchronously, and the clients replay transactions that were in progress and uncommitted to disk before the OST failure. - - - - - - - - - - - - - Lustre 2.0 Operations Manual - 821-2076-10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Copyright © 2011, Oracle and/or its affiliates. All rights reserved. -
+ -- 1.8.3.1