<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.4. What if Two Nodes Have the Same Score</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican 1.6" /><meta name="package" content="Pacemaker-Pacemaker_Explained-1.1-en-US-1-0" /><link rel="home" href="index.html" title="Configuration Explained" /><link rel="up" href="s-resource-location.html" title="6.2. Deciding Which Nodes a Resource Can Run On" /><link rel="prev" href="ch06s02s03.html" title="6.2.3. Symmetrical "Opt-Out" Clusters" /><link rel="next" href="s-resource-ordering.html" title="6.3. Specifying the Order Resources Should Start/Stop In" /></head><body class=""><p id="title"><a class="left" href="https://fedorahosted.org/publican"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="https://fedorahosted.org/publican"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s-resource-ordering.html"><strong>Next</strong></a></li></ul><div class="section" title="6.2.4. What if Two Nodes Have the Same Score"><div class="titlepage"><div><div><h3 class="title" id="node-score-equal">6.2.4. What if Two Nodes Have the Same Score</h3></div></div></div><div class="para">
If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know what was intended.
</div><div class="example" id="id3890921"><div class="example-contents"><pre class="programlisting">
<constraints>
<rsc_location id="loc-1" rsc="Webserver" node="sles-1" score="INFINITY"/>
<rsc_location id="loc-2" rsc="Webserver" node="sles-2" score="INFINITY"/>
<rsc_location id="loc-3" rsc="Database" node="sles-1" score="500"/>
<rsc_location id="loc-4" rsc="Database" node="sles-2" score="300"/>
<rsc_location id="loc-5" rsc="Database" node="sles-2" score="200"/>
</constraints>
</pre></div><h6>Example 6.3. Example of two resources that prefer two nodes equally</h6></div><br class="example-break" /><div class="para">
In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node's uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s03.html"><strong>Prev</strong>6.2.3. Symmetrical "Opt-Out" Clusters</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s-resource-ordering.html"><strong>Next</strong>6.3. Specifying the Order Resources Should Start/...</a></li></ul></body></html>
