Coordinator Service

Find out more about the coordinator service.

The coordinator is a microservice whose responsibility is to perform failover and failback of the Netcool® Operations Insight® deployments. Both primary and backup Netcool Operations Insight deployments should have coordinator service running for successful failover and failback between them. Therefore, the primary deployment must run the coordinator in primary state while the backup deployment must run the coordinator in default backup state. Find out more about different states in the States section.

The coordinator service in backup deployment tries to connect to the primary coordinator service through the HAProxy to determine the state of the backup deployment. If the primary is not reachable, the backup coordinator service does the failover, which means it changes its state to Acting Primary. It keeps polling the primary when in Acting Primary state so that it can do failback when primary is reachable again in the future. The backup coordinator service can be configured to use multiple proxies to communicate with the primary service to mitigate against proxy failures. All those proxy endpoints can be mentioned at the time of backup deployment set up.

Ensure you created the correct secrets and configuration map to run the coordinator service. Read the Setting up the coordinator service section for more information.

States

The Netcool Operations Insight deployment can be in different states. The Primary Deployment Service States are:

• Primary: when the grouping and enrichment of live events is enabled.
• Primary Maintenance: when the grouping and enrichment of live events that are disabled and system in maintenance mode​.

The Backup Deployment Service States are:

• Backup: when the backup system is not grouping and enriching events and is checking the status of the primary deployment for liveness​.
• Acting Primary: when the backup system is grouping and enriching events and is checking when to auto failback.​
• Acting Primary No Auto Fail Back: when the backup system is Acting Primary but is not checking for auto failback. Useful when in maintenance mode.

The relationships between the states are explained in Figure 1 and 2. You can see that the Primary States communicate by using manual API and the Backup States can use both manual or automatic API.