ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaig_5.4.0.1/rzaigconceptsrejoin.htm

77 lines
5.8 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Rejoin" />
<meta name="abstract" content="Rejoin means to become an active member of a cluster after having been a nonparticipating member." />
<meta name="description" content="Rejoin means to become an active member of a cluster after having been a nonparticipating member." />
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsevents.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsrejoinexample.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigmanagestartnode.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootchangepartitionednodes.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaigconceptsrejoin" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Rejoin</title>
</head>
<body id="rzaigconceptsrejoin"><a name="rzaigconceptsrejoin"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Rejoin</h1>
<div><p><dfn class="term">Rejoin</dfn> means to become an active member of a cluster
after having been a nonparticipating member.</p>
<p>For example, when clustering is restarted on a node after the node has
been inactive, the cluster node rejoins the cluster. You start cluster resource
services on a node by starting it from a node that is already active in the
cluster. Beginning with cluster version 3, a node can start itself and will
be able to rejoin the current active cluster, provided it can find an active
node in the cluster. See Start a cluster node for details.</p>
<p>Suppose that nodes A, B, and C make up a cluster. Node A fails. The active
cluster is now nodes B and C. Once the failed node is operational again, it
can rejoin the cluster when the node is started from any cluster node, including
itself. The rejoin operation is done on a cluster resource group basis, which
means that each cluster resource group (CRG) joins the cluster independently.</p>
<p>The primary function of rejoin ensures that the CRG object is replicated
on all active recovery domain nodes. The rejoining node, as well as all existing
active cluster nodes, must have an identical copy of the CRG object. In addition,
they must have an identical copy of some internal data.</p>
<p><img src="./delta.gif" alt="Start of change" />If there are nodes in the cluster administrative domain
that are not active, any resource changes that are made in the active domain
will be propagated to the inactive nodes once they rejoin the active domain.<img src="./deltaend.gif" alt="End of change" /></p>
<p><img src="./delta.gif" alt="Start of change" />When a node fails, the continued calling of
cluster resource services on the remaining nodes in the cluster can change
the data in a CRG object. The modification must occur due to the calling of
an API or a subsequent node failure. For simple clusters, the rejoining node
is updated with a copy of the CRG from some node that is currently active
in the cluster. However, this may not be true in all cases.<img src="./deltaend.gif" alt="End of change" /></p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaigconceptsrejoinexample.htm">Example: Rejoin</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
<span><img src="./delta.gif" alt="Start of change" />This topic describes the actions
that can occur when a node rejoins a cluster.<img src="./deltaend.gif" alt="End of change" /></span></li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <img src="./delta.gif" alt="Start of change" /><a href="rzaigconceptsevents.htm" title="Within a cluster several types events, actions, and services can occur.">Cluster events</a><img src="./deltaend.gif" alt="End of change" /></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaigmanagestartnode.htm" title="Starting a cluster node starts cluster resource services on a node in the cluster. Beginning with cluster version 3, a node can start itself and will be able to rejoin the current active cluster, provided it can find an active node in the cluster.">Start a cluster node</a></div>
<div><a href="rzaigtroubleshootchangepartitionednodes.htm" title="Sometimes, a partitioned condition is reported when there really was a node outage. This can occur when cluster resource services loses communications with one or more nodes, but cannot detect if the nodes are still operational. When this condition occurs, a simple mechanism exists for you to indicate that the node has failed.">Change partitioned nodes to failed</a></div>
</div>
</div>
</body>
</html>