4.3.2 Master Jobs High Availability
- This feature provides a self-resiliency to the master jobs in the application against the failure of a master node on which these master jobs are running.
- One of the active application instances will get designated as a master and starts the master jobs on its node.
- On a graceful shutdown of a master node, it de-registers itself as a master and allows one of the other active application instances to take over as a master and the new master node will start the master jobs.
- On a crash scenario, a health check job running on all the nodes will designate one of the application instances as a master. This new master will start the master jobs.
- In either of a scenario (graceful shutdown or crash), the master node switch-over will happen only during the next run of a health check job, so a little delay in switch-over can be expected Application instance will get a unique value allocated for server.id internally.
Parent topic: High Availability Changes