[Pacemaker] "No respawn" for cluster resources

[Stallmann, Andreas]

Hi!

When the tomcat daemon dies in our master/slave cluster (for some reason), crm tries to restart it.

We don’t want that, because the restart of the daemon takes longer than the promote of the slave to master state.

I figure that trying to restart a resource on a node is the “normal” behaviour, right?

Is there a way to stop crm/pacemaker from doing that?

The only thought we came up with is to set a location constrain for the “failed master” to a negative value, if monitor reports an error, but we fear that this leads to trouble during startup, when tomcat (or the URL we’re checking) is not up for quite a while.

Any better ideas?

Thanks in advance,

Andreas

--
CONET Solutions GmbH
Andreas Stallmann,
Theodor-Heuss-Allee 19, 53773 Hennef
Tel.: +49 2242 939-677, Fax: +49 2242 939-393
Mobil: +49 172 2455051
Internet: http://www.conet.de, mailto: AStallmann at CONET.DE<mailto:AStallmann at CONET.DE>



----------------------------
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)
Geschäftsführer/Managing Director: Anke Höfer

 ----------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120727/bd19f5e3/attachment-0002.html>