Hi!
TNX for your answer. We will switch to sbd after the shared storage has been
set up.
For now, I need an interim solution, which is, as of now, stonith via suicide.
My configuration doesn't work, though.
I tried:
~~~~~~Output from crm configure show~~~~~~~~~~
primitive suicide_res stonith:suicide
...
clone fenc_clon suicide_res
...
property $id="cib-bootstrap-options" \
dc-version="1.1.2-8b9ec9ccc5060457ac761dce1de719af86895b10" \
cluster-infrastructure="openais" \
expected-quorum-votes="3" \
stonith-enabled="true" \
no-quorum-policy="suicide" \
stonith-action="poweroff"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If I disconnect one node from the network, crm_mon shows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Current DC: mgmt03 - partition WITHOUT quorum
...
Node mgmt01: UNCLEAN (offline)
Node mgmt02: UNCLEAN (offline)
Online: [ mgmt03 ]
Clone Set: fenc_clon
Started: [ ipfuie-mgmt03 ]
Stopped: [ suicide_res:0 suicide_res:1 ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No action, neither reboot nor poweroff is taken.
1. What did I do wrong here?
2. OK, let's be more precise: I have the feeling, that the "suicide" ressource
should be in a default state of "stopped" (on all nodes) and should only be
started on the node, which has to fence itself. Am I right? And, if yes, how is
that accomplished?
3. How does the "no-quorum-policy" relate to the stonith-ressources? I didn't
find any documentation, if the two have any connection at all.
4. Am I correct, that the "no-quorum-policy" is what a node (or a cluster
partition) should do to itself, when it looses quorum (for example, shut down
itself), and stonith is what the nodes with quorum try to do to the nodes
without?
5. Shouldn't then "no-quorum-policy=suicide" be obsolet in case of suicide as
stonith-method?
TNX for your help (again),
Andreas
------------------------
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)
Geschäftsführer/Managing Directors: Jürgen Zender (Sprecher/Chairman), Anke
Höfer
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Hans Jürgen
Niemeier
CONET Technologies AG, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 10328 )
Vorstand/Member of the Managementboard: Rüdiger Zeyen (Sprecher/Chairman),
Wilfried Pütz
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Gerd
Jakob
_______________________________________________
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
