Lead your team forward
OCT 24 / 9AM ET Register nowHigh 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.
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:
#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:
#MDM HTTP server
ataccama.server.http.default.port=8051
ataccama.server.http.default.path.exclude=/,/console/**,/api/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=/api/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=rest
Configure High Availability Implementation
High availability implementation uses database locking (see HA Database Locking and Leadership Election) and is configured in MDM Server application.properties (MDM Server Application Properties):
Name | Default Value | Description |
---|---|---|
|
db |
HA implementation setting.
The default value selects the DB locking.
Setting the value to |
|
15s |
|
|
20s |
|
|
8058 |
|
|
default |
|
|
$\{ataccama.server.http.$\{ataccama.one.mdm.ha.local-target-server.name}.port} |
|
|
mdm-server_1 |
|
|
false |
Enable the Disconnect button in the HA console. |
|
0.0.0.0 |
|
|
<assigned automatically> |
Visible in the HA console.
Overrides the |
|
mdc_db |
HA database name. |
|
ha_ |
Lock and HA Node table prefix. |
|
MDM_LEADER_INSTANCE |
Key for the HA leader instance. |
|
5000 |
Interval at which the HA tables are updated. |
|
30000 |
Interval at which expired entries are removed from the HA tables. |
|
30000 |
Entries older than this interval are marked as expired. |
|
5000 |
Interval at which the leadership election workflow is called. |
|
$\{random.int(10000)} |
Start delay of the leadership election workflow. |
|
3s |
|
|
4s |
Was this page useful?