Watchdog Configuration
The watchdog applications are installed in each instance separately. To enable watchdogs, some parameters should be defined in the System Config Man, after which the sc-watchdog service should be restarted.
- Navigate to Administration > System Config Management.
- Set the following parameters and Save:
Value | Definition | ๏ปฟ |
netright.job.master.instance.name | Instance name | Master instance parameter for the controller region. It must be the same as the one defined in netright.properties. |
netright.job.master.instance.name.$region_name | Instance name | Master instance parameter for the controlled region. It must be the same as the one defined in netright.properties. |
watchdog.check.attempt.num | integer | Number of times the watchdog should check the status before initiating the failover scenario. |
watchdog.check.interval | integer | How often the watchdogs should communicate with each other. |
watchdog.interregion.communication | boolean | The default value is "false". If the parameter value is changed to "true", instance acknowledgments are accessible from, not only within regions, but across the whole environment. |
watchdog.stop.sapm.jobs.after.down.instance | boolean | The default value is "false". If the parameter value is changed to "true", the watchdog application will do the following checks: - If the status of a master instance is down, or - If the watchdog of a master instance is unavailable, or - If the replication status is not active for one of the master instances; Enabled SAPM Jobs are disabled for all instances in the environment. - After these undesired conditions are eliminated, the disabled SAPM Jobs are changed back to Enabled to trigger. Watchdog does not interfere with activity jobs, just change their status in the database. When the status of these jobs is disabled, they are not executed. They are only executed when the status is set to โenabledโ again. |
After configuring these parameters, the sc-watchdog service should be restarted.