On 14 Jan 2014, at 3:52 pm, renayama19661...@ybb.ne.jp wrote: > Hi All, > > I contributed next bugzilla by a problem to occur for the difference of the > timing of the attribute update by attrd before. > * https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2528 > > We can evade this problem now by using crmd-transition-delay parameter. > > I confirmed whether I could evade this problem by renewed attrd recently. > * In latest attrd, one became a leader and seemed to come to update an > attribute. > > However, latest attrd does not seem to substitute for crmd-transition-delay. > * I contribute detailed log later. > > We are dissatisfied with continuing using crmd-transition-delay. > Is there the plan when attrd handles this problem well in the future?
Are you using the new attrd code or the legacy stuff?
If you're not using corosync 2.x or see:
crm_notice("Starting mainloop...");
then its the old code. The new code could also be used with CMAN but isn't
configured to build for in that situation.
Only the new code makes (or at least should do) crmd-transition-delay redundant.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
