If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

High Availability Configuration

This section provides an overview of high availability configuration for MDM. Detailed instructions are covered in sections dedicated to particular topics.

Prerequisites and Dependencies

The MDM server and its dependencies are configured on each MDM node, see MDM Configuration.
MDM high availability setup requires an in-house load balancer/router solution.
The RDBMS used as MDM persistence should operate in the highly available mode too (as well as other dependencies). These configurations are independent of MDM and should be prepared in-house.

Install Zookeeper

As a first step, install Zookeeper and configure a cluster (ensemble) with at least three Zookeeper servers. Follow the instructions in the Zookeeper documentation: zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html#sc_zkMulitServerSetup. For an overview of Zookeeper, see Zookeeper Overview.

TickTime, initLimit and syncLimit must be same for all servers on a cluster.

Also, it is recommended to use autopurge.snapRetainCount=3 and autopurge.purgeInterval=1 to delete old logs. Zookeeper data folder can get quite big (tens of GBs in a few days if not purged).

Configure the HTTP Server

The MDM HTTP Server is configured in the MDM Server application.properties (see MDM Server Application Properties).

By default, it uses one port for the HA Admin Console (HA Admin Console) and the HA REST, and another port for the HA load balancer:

Default MDM HTTP Server configuration for HA

#MDM HTTP server
ataccama.server.http.default.port=8051

#HA configuration
ataccama.one.mdm.ha.load-balancer.port=8058

Alternatively, you can configure separate ports for the HA console and HA REST using the path.exclude and path.include properties as seen in the following example:

Example of advanced MDM HTTP Server configuration for HA with separate ports

#MDM HTTP server
ataccama.server.http.default.port=8051
ataccama.server.http.default.path.exclude=/,/console/**,/nme-rest/**,/ha/console/**,/ha/rest/**
ataccama.server.http.console.port=8052
ataccama.server.http.console.path.include=/,/console/**,/sso/**,/health
ataccama.server.http.rest.port=8053
ataccama.server.http.rest.path.include=/nme-rest/**
ataccama.server.http.ha-console.port=8054
ataccama.server.http.ha-console.path.include=/ha/console
ataccama.server.http.ha-rest.port=8055
ataccama.server.http.ha-rest.path.include=/ha/rest

#MDM HA configuration
ataccama.one.mdm.ha.load-balancer.port=8058
ataccama.one.mdm.ha.local-target-server.name=nme-rest

Configure High Availability Component

High availability component is an Ataccama Zookeeper client configured on each MDM instance. The component communicates with Zookeeper and switches MDM between the RW and RO modes. See High Availability Component for component configuration reference.

Was this page useful?