Attached are patches for the Active - Passive chapter of "Clusters From Scratch".
# HG changeset patch # User Marcus Barrow <mbar...@redhat.com> # Date 1301591444 14400 # Node ID 51a928853a59b284962b4db9fd2c65c9659e0452 # Parent b0679c787b9120526546a37709e7c7628adf57bc [mq]: CS-Active-Passive diff -r b0679c787b91 -r 51a928853a59 doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.xml --- a/doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.xml Thu Mar 31 11:29:01 2011 -0400 +++ b/doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.xml Thu Mar 31 13:10:44 2011 -0400 @@ -324,12 +324,12 @@ <section> <title>Prevent Resources from Moving after Recovery</title> <para> - In some circumstances it is highly desirable to prevent healthy resources from being moved around the cluster. Move resources almost always requires a period of downtime and for complex services like Oracle databases, this period can be quite long. + In some circumstances it is highly desirable to prevent healthy resources from being moved around the cluster. Moving resources almost always requires a period of downtime. For complex services like Oracle databases, this period can be quite long. </para> <para> To address this, Pacemaker has the concept of resource stickiness which controls how much a service prefers to stay running where it is. You may like to think of it as the âcostâ of any downtime. By default, Pacemaker assumes there is zero cost associated with moving resources and will do so to achieve âoptimal<footnote> <para> - It should be noted that Pacemakerâs definition of optimal may not always agree with that of a humanâs. The order in which Pacemaker processes lists of resources and nodes create implicit preferences (required in order to create a stabile solution) in situations where the administrator had not explicitly specified some. + It should be noted that Pacemakerâs definition of optimal may not always agree with that of a humanâs. The order in which Pacemaker processes lists of resources and nodes creates implicit preferences in situations where the administrator has not explicitly specified them. </para> </footnote>â resource placement. We can specify a different stickiness for every resource, but it is often sufficient to change the default. </para>
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
