<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid">
<DIV class=plainMail><BR>>> start resource steps<BR>>> step(1)<BR>>> crm configure primitive?vol_mpath0 ocf:heartbeat:Filesystem meta target->role=stopped params device=/dev/mapper/mpath0 >directory=/mnt/mapper/mpath0 fstype='lustre' op start timeout=300s? op stop >timeout=120s op monitor timeout=120s interval=60s op notify timeout=60s<BR>>> step(2)crm resource reprobe<BR>><BR>> >step(3)<BR>> >crm configure location vol_mpath0_location_manage?datavol_mpath0 rule -inf: not_defined pingd_manage or pingd_manage lte 0<BR>>><BR>> >crm configure location vol_mpath0_location_data?datavol_mpath0 rule -inf: >not_defined pingd_data or pingd_data lte 0<BR><BR>>why do you have 2 location constraints? where is the definitions for<BR>>pingd_data and pingd_manage?<BR></DIV>
<DIV class=plainMail>because we have two network. manage network is ethernet data network is ib.</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>the definitions of pingd</DIV>
<DIV class=plainMail>crm configure primitive pingd_data ocf:pacemaker:ping meta target-role=stopped params name=pingd_data op start timeout=100s op stop timeout=100s op monitor interval=90s timeout=100s";</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm_resource -p host_list -r pingd_data -v IP_list</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm configure clone pingd_data_net pingd_data meta globally-unique=falsetarget-role=stopped</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm resource start pingd_data</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm configure primitive pingd_manage ocf:pacemaker:ping meta target-role=stopped params name=pingd_manage op start timeout=90s op stop timeout=100s op monitor interval=90s timeout=100s</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm_resource -p host_list -r pingd_manage -v IP_list</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm configure clone pingd_manage_net pingd_manage meta globally-unique=false</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>crm resource start pingd_manage</DIV>
<DIV class=plainMail><BR>><BR>> >step(4)<BR>> .crm resource start vol_mpath0<BR>><BR>> >delete resource steps<BR>><BR>> .step(1)<BR>> >crm resource stop vol_mpath0<BR>><BR>> >step(2)<BR>> >crm resource cleanup vol_mpath0<BR>><BR>> >step(3)<BR>> >crm configure delete vol_mpath0<BR>><BR>> >above?is my steps? is it right? I repeat these steps for several times. at begin >>it works well. after 5 or 6 times the reosurce could not start .I use crm resource >>start vol_mpath0 again no use.<BR><BR>>Could be that your ping nodes are down?<BR>the node is ok. and do you know the way to check pingd? and I found the cluster is something wrong.I check the log I think node could not get the situation from crm</DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail> </DIV>
<DIV class=plainMail>><BR>> my pacemaker package?are<BR>> ? ? pacemaker-1.0.8-6.1.el5<BR>> ? ? pacemaker-libs-devel-1.0.8-6.1.el5<BR>> ? ? pacemaker-libs-1.0.8-6.1.el5<BR>><BR>> ? ? openais packages?are<BR>> ? ? openaislib-devel-1.1.0-1.el5<BR>> ? ? openais-1.1.0-1.el5<BR>> ? ? openaislib-1.1.0-1.el5<BR>><BR>> ??? corosync packages are<BR>> ? ? corosync-1.2.2-1.1.el5<BR>> ? ? corosynclib-devel-1.2.2-1.1.el5<BR>> ? ? corosynclib-1.2.2-1.1.el5<BR>> ? ? who know why thanks a lot<BR>><BR>><BR>> _______________________________________________<BR>> Pacemaker mailing list: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>><BR>> Project
Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>> Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>> Bugs: <A href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR>><BR><BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Fri, 12 Nov 2010 13:07:56 -0500<BR>From: Vadym Chepkov <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=vchepkov@gmail.com" ymailto="mailto:vchepkov@gmail.com">vchepkov@gmail.com</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org"
ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] 2 node failover cluster + MySQL Master-Master<BR> replica setup<BR>Message-ID: <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=12802784-1613-4EF6-81FF-7B91F2B3BA33@gmail.com" ymailto="mailto:12802784-1613-4EF6-81FF-7B91F2B3BA33@gmail.com">12802784-1613-4EF6-81FF-7B91F2B3BA33@gmail.com</A>><BR>Content-Type: text/plain; charset=us-ascii<BR><BR><BR>On Nov 12, 2010, at 11:14 AM, Ruzsinszky Attila wrote:<BR><BR>> Hi,<BR>> <BR>>> And now (officially) RHCS can also use Pacemaker<BR>>> <A href="http://theclusterguy.clusterlabs.org/post/1551292286" target=_blank>http://theclusterguy.clusterlabs.org/post/1551292286</A><BR>> Nice.<BR>> <BR>>> Yeah, like I said, Master-Master and Pacemaker without a proper resource<BR>>> agent will cause issues.<BR>> Yes.<BR>> <BR>>> big
problems. Now let me explain this, a 2-node Multi-Master MySQL setup<BR>>> means setting up every node as both Master and Slave, node 1's Master<BR>>> replicates asynchronously to node 2's Slave and node 2's Master replicates<BR>>> asynchronously to node 1's Slave. The replication channels between the two<BR>>> are not redundant, nor do they recover from failure automatically and you<BR>>> have to manually set the auto-increment-increment and auto-increment-offset<BR>>> so that you don't have primary key collisions.<BR>> Clear.<BR>> <BR>>> each server. Looking at how DRBD handles these kinds of things is one way to<BR>>> go about it, but ... it's a huge task and there are a lot of things that can<BR>>> go terribly wrong.<BR>> :-(<BR>> <BR>>> So again, for the third time, the problem is not the Multi-Master setup, nor<BR>>> it is Pacemaker, it's just a very specific use case
for which a resource<BR>>> agent wasn't written.<BR>> OK.<BR>> So now almost the only one possibilities is DRBD+MySQL?<BR>> <BR><BR>I am pretty sure Linbit announced mysql RA with replication capabilities. Haven't seen documentation though.<BR><BR>Vadym<BR><BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Pacemaker mailing list<BR><A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR><A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR><BR><BR>End of Pacemaker Digest, Vol 36, Issue 47<BR>*****************************************<BR></DIV></BLOCKQUOTE></td></tr></table><br>