Hi, I was looking into the SystemHealth feature a little bit deeper and I noticed perhaps a little design error:
Given you have a HealthAgent that monitors the CPU load on one node and the Health-Strategy set to "migrate on red". Now you clone that Agent to measure the CPU load on all nodes. Now the Load on one system goes up, the #health-cpu attribute goes "red" and all resources move away from the node. Of course the instance of the SystemHealth clone that measures the load also moves away from that node. Thus it cannot measure the cpu load of the node any more and the attribute stays on "red" even if the load drop below the limits. The admin must remove attribute manually to allow the clone instance (and all other resoruces) to be started on that node again. Not a very nice situation. Perhaps it would be better the make all Health-RAs to ignore the Health- Strategy. Greetings, -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [email protected] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
