High availability and disaster recovery in a Data Engineering domain

High availability and disaster recovery in a Data Engineering domain

High availability for the Metadata Access Service

High availability for the Metadata Access Service

High availability for the Metadata Access Service minimizes interruptions while fetching metadata at design time and enables the domain to react to network failures and failures of the Metadata Access Service.
When a Metadata Access Service process becomes unavailable, the Service Manager tries to restart the process or fails the process over to another node based on the service configuration.
The restart and failover behavior depends on the following ways that you can configure the Metadata Access Service:
Single node
When the Metadata Access Service runs on a single node and the service process shuts down unexpectedly, the Service Manager tries to restart the service process. If the Service Manager cannot restart the process, the process stops or fails.
Primary and backup nodes
When the Metadata Access Service runs on primary and backup nodes and the service process shuts down unexpectedly, the Service Manager tries to restart the service process. If the Service Manager cannot restart the process, the Service Manager fails the service process over to a backup node.
A Metadata Access Service process fails over to a backup node in the following situations:
  • The Metadata Access Service process fails and the primary node is not available.
  • The Metadata Access Service process is running on a node that fails.
The Service Manager restarts the Metadata Access Service process based on domain property values set for the amount of time spent trying to restart the service and the maximum number of attempts to try within the restart period.
The Metadata Access Service clients are resilient to temporary connection failures during restart and failover of the service.

0 COMMENTS

We’d like to hear from you!