On 09/03/2009 11:26 AM, Florian Haas wrote: > Why not simply report $OCF_NOT_RUNNING on monitor, and let the CRM > handle the restart? That way you'll actually have the CRM keep tabs on > failures via failcount, and give it the possibility to react.
i came across some mysql-proxy hangs that the mysql-proxy ra in its current, commited state, was unable to catch. currently, the ra is not doing any in-depth monitoring and i figured that mysql-proxy might have better methods to check its own vitality. moreover, i think it is ok to expose useful options (see above) to the user. regarding the monitoring action: future enhancements might be to issue a query using something similar to the mysql ra's check (think test_user, test_table, etc.) another thought i have got is to add a check via the mysql proxy admin module, but currently, there is no admin.lua script shipped with the debian package so i'm still considering what to do in this case. so to sum things up, i do not think it is a bad idea to let the user choose, if he wants to use the proxy's keepalive. nobody is forced to do so and this option defaults to "false" anyways. cheers, raoul -- ____________________________________________________________________ DI (FH) Raoul Bhatia M.Sc. email. [email protected] Technischer Leiter IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email. [email protected] 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax. +43 1 3670030 15 ____________________________________________________________________ _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
