69 lines
5.2 KiB
HTML
69 lines
5.2 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="Merge" />
|
||
|
|
<meta name="abstract" content="A merge operation is similar to a rejoin operation except that it occurs when nodes that are partitioned begin communicating again." />
|
||
|
|
<meta name="description" content="A merge operation is similar to a rejoin operation except that it occurs when nodes that are partitioned begin communicating again." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsevents.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsmergeexample.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsrejoin.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigmanagestartnode.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootpartitionerrors.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="rzaigconceptsmerge" />
|
||
|
|
<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>Merge</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigconceptsmerge"><a name="rzaigconceptsmerge"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Merge</h1>
|
||
|
|
<div><p>A <dfn class="term">merge</dfn> operation is similar to a rejoin operation
|
||
|
|
except that it occurs when nodes that are partitioned begin communicating
|
||
|
|
again.</p>
|
||
|
|
<p>The partition may be a true partition in that cluster resource services
|
||
|
|
is still active on all nodes. However, some nodes cannot communicate with
|
||
|
|
other nodes due to a communication line failure. Or, the problem may be that
|
||
|
|
a node actually failed, but was not detected as a failure.</p>
|
||
|
|
<p>In the first case, the partitions are merged back together automatically
|
||
|
|
once the communication problem is fixed. This happens when both partitions
|
||
|
|
periodically try to communicate with the partitioned nodes and eventually
|
||
|
|
reestablish contact with each other. In the second case, cluster resource
|
||
|
|
services must be restarted on the failed node by starting the node from any
|
||
|
|
node in the cluster.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaigconceptsmergeexample.htm">Example: Merge</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
Merge operations can occur in several different situations.</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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaigconceptsrejoin.htm" title="Rejoin means to become an active member of a cluster after having been a nonparticipating member.">Rejoin</a></div>
|
||
|
|
<div><a href="rzaigtroubleshootpartitionerrors.htm" title="Certain cluster conditions are easily corrected. If a cluster partition has occurred, you can learn how to recover. This topic also tells you how to avoid a cluster partition and gives you an example of how to merge partitions back together.">Partition errors</a></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>
|