Imagine that I have 3 resources. d_A, d_B and d_C. They all have to
run together on the same node however I want the behaviour upon failure
of a service to be different. If primitive d_A and d_B fail I want the
whole group to fail to another node. If primitive d_C fails I just want
it to restart.
So first of all , is this possible ? :)
At first I had my rsc_defaults migration-treshold set to 1 and changed
the value for the primitive d_C to infinity, however upon failing d_C
all resource migrated to the other node rather than just having d_C
restarted on the same node.
So I inverted my logic to by default restart all resources on the same
node, however this makes me wonder if the resource specific parameters
overrule the default ones or not.
property $id="cib-bootstrap-options" \
stonith-enabled="FALSE" \
no-quorum-policy=ignore \
start-failure-is-fatal="FALSE" \
pe-error-series-max="9" \
pe-warn-series-max="9" \
pe-input-series-max="9"
rsc_defaults $id="rsc_defaults-options" \
migration-threshold="1" \
failure-timeout="10" \
resource-stickiness="INFINITY"
primitive d_A lsb:A \
op monitor interval="10s"
primitive d_B lsb:B \
op monitor interval="10s"
primitive d_C ocf:ntc:tomcat \
params instance_name="MSS" \
monitor_urls="" \
monitor_use_ssl="no" \
op monitor interval="15s" \
on-fail="restart" \
migration-treshold="INFINITY"
timeout="30s"
primitive ip_A ocf:heartbeat:IPaddr2 \
params ip="<%= serviceIP %>" cidr_netmask="<%= servicePrefix %>"
nic="<%= serviceDevice %>" \
op monitor interval="10s"
group svc-ABC d_A d_B d_C ip_A
commit
Or shouldn't I be using group to group them ?
greetings
Kris
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
