Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Enterprise Data Preparation Service
  12. Interactive Data Preparation Service
  13. Informatica Cluster Service
  14. Mass Ingestion Service
  15. Metadata Access Service
  16. Metadata Manager Service
  17. Model Repository Service
  18. PowerCenter Integration Service
  19. PowerCenter Integration Service Architecture
  20. High Availability for the PowerCenter Integration Service
  21. PowerCenter Repository Service
  22. PowerCenter Repository Management
  23. PowerExchange Listener Service
  24. PowerExchange Logger Service
  25. SAP BW Service
  26. Search Service
  27. System Services
  28. Test Data Manager Service
  29. Test Data Warehouse Service
  30. Web Services Hub
  31. Application Service Upgrade
  32. Appendix A: Application Service Databases
  33. Appendix B: Connecting to Databases from Windows
  34. Appendix C: Connecting to Databases from UNIX or Linux
  35. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Metadata Access Service Restart and Failover

Metadata Access Service Restart and Failover

When a Metadata Access Service process becomes unavailable, the Service Manager restarts the Metadata Access Service process on the same node or on a backup node.
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.