On 06/21/2012 11:30 PM, David Vossel wrote: > ----- Original Message ----- >> From: "Phil Frost" <p...@macprofessionals.com> >> To: pacemaker@oss.clusterlabs.org >> Sent: Tuesday, June 19, 2012 4:25:53 PM >> Subject: Re: [Pacemaker] resources not migrating when some are not runnable >> on one node, maybe because of groups or >> master/slave clones? >> >> On 06/19/2012 04:31 PM, David Vossel wrote: >>> Can you attach a crm_report of what happens when you put the two >>> nodes in standby please? Being able to see the xml and how the >>> policy engine evaluates the transitions is helpful. >> >> The resulting reports were a bit big for the list, so I put them in a >> bug report: >> >> https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2652 > > We're reporting pacemaker issues to bugs.clusterlabs.org now. > > I took a look at the cib in case2 and saw this in the status for storage02. > > <transient_attributes id="storage02"> > <instance_attributes id="status-storage02"> > <nvpair id="status-storage02-probe_complete" name="probe_complete" > value="true"/> > <nvpair id="status-storage02-master-drbd_nfsexports.1" > name="master-drbd_nfsexports:1" value="10"/> > </instance_attributes> > </transient_attributes> > > storage02 will not give up the drbd master since it has a higher score that > storage01. This coupled with the colocation rule between test and the drbd > master, and the location rule to never run "test" on storage02 cause the > "test" resource to never run.... "test" has to run with the drbd master, and > the drbd master is stuck because of the transient attributes on a node "test" > can't run on, so "test" can't start. > > I don't understand why the transient attribute is there, or where it came > from yet.
This is added by the RA with the crm_master command. For example the drbd RA chooses this value from the current state of drbd to let Pacemaker promote best candidate. Regards, Andreas > > > -- Vossel > > >> I've also found a similar discussion in the archives, though I didn't >> find much help in it: >> >> http://oss.clusterlabs.org/pipermail/pacemaker/2010-November/008189.html >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: >> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > -- Need help with Pacemaker? http://www.hastexo.com/now
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
