[Pacemaker] long start time

[Andrew Beekhof]

On Fri, Dec 11, 2009 at 3:17 PM, Mark Horton <mark at nostromo.net> wrote:
> Hi,
>
> I have a resource that takes about 3 minutes to start.  It's a java
> app server and is a little slow to launch.  What I've noticed is while
> the app server is starting on one node, no other commands are executed
> on other nodes.

What does the rest of your configuration look like?
Are there ordering constraints on that resource?  If so, then the
behavior is to be expected.

>
> For instance, if I put node B into standby, it will not take any
> actions needed to put node B into standby while node A is launching
> the app server process.  Once the app server has launched, it will
> then stop the resources on node B.
>
> This isn't a big problem but was mostly curious about it.  Are there
> any options that control this behavior?
>
> I'm using pacemaker 1.0.6 and corosync 1.1.2 downloaded from
> http://www.clusterlabs.org/rpm/
>
> Regards,
> Mark
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>