Hi Satomi-san, On Tue, Oct 14, 2008 at 07:07:00PM +0900, Satomi TANIGUCHI wrote: > Hi, > > I found that there are 2 problems when DC node is STONITH'ed. > (1) STONITH operation is executed two times.
This has been discussed at length in bugzilla, see http://developerbugs.linux-foundation.org/show_bug.cgi?id=1904 which was resolved with WONTFIX. In short, it was deemed to risky to implement a remedy for this problem. Of course, if you think you can add more to the discussion, please go ahead. > (2) Timeout-value which stonithd on DC node waits to reply > the result of STONITH op from other node is > always set to "stonith-timeout" in <cluster_property_set>. > [...] > The case (2): > When this timeout occurs on stonithd on DC > during non-DC node's stonithd tries to reset DC, > DC-stonithd will send a request to other node, > and two or more STONITH plugins are executed in parallel. > This is a troublesome problem. > The most suitable value as this timeout might be > the sum total of "stonith-timeout" of STONITH plugins on the node > which is going to receive the STONITH request from DC node, I think. This would probably be very difficult for the CRM to get. > But DC node can't know that... > I would like to hear your opinions. Sorry, but I couldn't exactly follow. Could you please describe it in terms of actions. Thanks, Dejan > Best Regards, > Satomi TANIGUCHI > _______________________________________________________ > Linux-HA-Dev: [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev > Home Page: http://linux-ha.org/ _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
