[Pacemaker] crm commands are blocked by starting services

[Andrew Beekhof]

On 14 Jul 2014, at 7:01 pm, Johan Huysmans <johan.huysmans at inuits.be> wrote:

> Hi All,
> 
> I noticed that any changes made with crm are not applied to the cluster configuration when a resource is being started.
> 
> I have a resource which can take some time to be started (2minutes). Whenever such resource is started any change made by executing the crm command is hold until the start is finished.
> 
> I changed my start function from my OCF so it will start fast and added the startup-delay for my monitoring. However this gave the same result. Between the start and the 1st monitor my changed made by crm are not applied.

We can't act on any changes (or failures) until the current actions complete.
There was talk that we could be able to change this behavior, but no-one has written it yet.

Maybe after .12 is done.


> 
> 
> 
> Is this expected behaviour, can this be tweaked by some configuration or is this a bug ?
> 
> I'm using version: 1.1.11-2bc1061
> 
> 
> Thanks for any insight in this problem.
> 
> Greetings,
> Johan
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140715/daccf757/attachment-0003.sig>