Some more relevant info:<br><br>OS: RHEL 5.6<br>Pacemaker: 1.0.11<br>Corosync 1.2.8<br>OpenAIS 1.1.4<br><br><br>Would I be better off dumping the group all together and just using location and ordering? I thought that was what groups were supposed to take care of, to simplify the configuration and restraints.<br clear="all">
<br>Bobbie Lind<br>Systems Engineer<br><i><b>Solutions Made Simple, Inc (SMSi)</b></i><br>
<br><br><div class="gmail_quote">On Thu, Aug 11, 2011 at 8:43 AM, Bobbie Lind <span dir="ltr"><<a href="mailto:blind@sms-fed.com">blind@sms-fed.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm having a hard time trying to understand the scoring that is displayed for a Resource group.<br><br>I'm trying to accomplish a Resource group with two resources (an LVM and a LUN) that runs in an Active/Passive method, that only attempts to run on two nodes the Primary s02ns070 and the secondary s02ns090.<br>
<br>Everything appears to work correctly for s02ns070 (Primary node) except that the scoring for the group_color and native_color of the lun (resMDT0000) is not displaying properly, see snip below (but it works).<br>The backup node s02ns090 does not seem to have the proper scoring for the native_color for both the LVM and the LUN. It currently shows -1000000, which is why it's not failing over.<br>
<br>I'm trying to figure out where the -1000000 score is coming from.<br><br>Here are the relevant portions of my config file:<br><br><snip><br>primitive resMDT0000 ocf:heartbeat:Filesystem \<br> meta target-role="Started" \<br>
operations $id="resMDT0000-operations" \<br> op monitor interval="120" timeout="60" \<br> op start interval="0" timeout="300" \<br> op stop interval="0" timeout="300" \<br>
params device="/dev/mapper/dsdw_mdt_vg-dsdw_mdt_vol" directory="/lustre/dsdw-MDT0000" fstype="lustre"<br>primitive resMDTLVM ocf:heartbeat:LVM \<br> params volgrpname="dsdw_mdt_vg"<br>
group MDSgroup resMDTLVM resMDT0000<br>location locMDSprimary MDSgroup inf: s02ns070<br>location locMDSsecondary MDSgroup 5000: s02ns090<br>colocation colocMDSOSS1 -inf: anchorOSS1 MDSgroup<br>colocation colocMDSOSS2 -inf: anchorOSS2 MDSgroup<br>
colocation colocMDSOSS3 -inf: anchorOSS3 MDSgroup<br>colocation colocMDSOSS4 -inf: anchorOSS4 MDSgroup<br><snip><br><br>On first startup of the cluster the following scores are set to the relevant nodes: found using ptest -Ls<br>
<br><snip><br>group_color: MDSgroup allocation score on s02ns070: 1000000<br>group_color: MDSgroup allocation score on s02ns090: 5000<br>group_color: resMDTLVM allocation score on s02ns070: 1000000<br>group_color: resMDTLVM allocation score on s02ns090: 5000<br>
<br>group_color: resMDT0000 allocation score on s02ns070: 0<br>group_color: resMDT0000 allocation score on s02ns090: 0<br><br>native_color: resMDTLVM allocation score on s02ns070: 1000000<br>native_color: resMDTLVM allocation score on s02ns090: -1000000<br>
<br>native_color: resMDT0000 allocation score on s02ns070: 0<br>native_color: resMDT0000 allocation score on s02ns090: -1000000<br><snip><br><br>On top of this the secondary node is trying to start resources that it shouldn't have access to (according to how I think I have colocation set up)<br>
<br>I have attached an hb_report from the time I start both nodes until it settles in the odd configuration of primary node holding the resource and the secondary node trying to start other seemingly random resources.<br>
<br>I have looked into the Asymmetrical "opt-in" clusters from <a href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ch06s02s02.html" target="_blank">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ch06s02s02.html</a> and I am wondering if this will fix some (if not all) of my issues with the secondary node. I have also checked out the Master/Slave configuration but I'm not sure that's what I am looking for since LVMs and the LUN can not (and should not) be started in more than one place.<br>
<br>My questions are:<br>1) Why does the resource resMDT0000 not seem to pull the proper scoring both in the group_color or that native_color? And what is it about my configuration that I set up wrong to make this happen?<br>
2) Is there a way to 'reset' scoring or force a score recalculation?<br>3) What would be the proper debug tool to use to find out where and what is changing/affecting the scores?<br><br>Any help would be greatly appreciated.<br>
<font color="#888888">
<br clear="all"><br>Bobbie Lind<br>Systems Engineer<br><i><b>Solutions Made Simple, Inc (SMSi)</b></i><br><br>
</font></blockquote></div><br>