I am a bit confused here. Is HAFW a part of confD or is it some external cluster resource management software?
As I can see in the UG, it states
The remaining slaves must also be informed by the HAFW about the new master situation. ConfD will never take any actions regarding master/slave-ness by itself..
Which HAFW is it talking about?
It further states
The only thing ConfD does is to replicate the CDB data amongst the members in the HA group. It doesn't perform any of the otherwise High-Availability related tasks such as running election protocols in order to elect a new master.
How do I achieve election protocol stuff for electing a new master?
I have a few more questions here but before asking I would like to give a brief on my system architecture. So I have like two management blades in a chassis-based system which are to be configured over a high availability network. I have tested with configuring the management blades over confD high availability and the CDB is getting synced and also the changes are getting replicated during configuration changes.
Now my questions are:-
- How do I achieve election of a new master when the master/active node goes down or when the socket connection is closed?
- How do I achieve a single point of access to the confD server for all of my managed object nodes (Floating Virtual IP)?
- Do I have to re-initiate the CDB subscription to the new master node when the master/active node goes down?
- What impact does this overall high availability switch over have on my managed objects?
- At what conditions do I need to make use of HA notifications?
- Do I have to use any cluster resource management software (eg. corosync, pacemaker, etc.) on top of confD?
- If I do have to use external HAFWs, which HAFW fits well will confD?