Hi All, The crmd-transition-delay waits for the update of the attribute to be late.
However, crmd cannot realize the wait of the attribute well because a timer is not reset when the delay of the attribute occurs after a timer was set. As a result, the resource may not be placed definitely. I wrote a patch for Pacemaker 1.0.12. And this patch blocks the handling of tengine when a crmd-transition-delay timer is set. And tengine handles instructions of pengine after a crmd-transition-delay timer exercised it definitely. By this patch, the start of the resource may be late. However, it realizes the placement of a right resource depending on limitation. * I think that the similar correction is necessary for a development version of Pacemaker. Best Regards, Hideo Yamauchi.
1891.patch
Description: Binary data
_______________________________________________ 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
