In Ambari 2.4.0.0, adding or removing Atlas Metadata Servers
requires manually editing the atlas.rest.address property.
-
In Ambari Web, click Hosts, then
select the host on which to install the standby Atlas Metadata Server.
-
On the Summary page of the new Atlas Metadata Server host,
click .
-
Complete the wizard steps to add the new Atlas Metadata Server.
Ambari adds the new Atlas Metadata Server in a Stopped state.
-
On Services, browse to .
-
In Advanced application-properties, append the
atlas.rest.address property with a comma and the value for the
new Atlas Metadata Server.
atlas.rest.address
property,http(s):[HOST_NAME]:[PORT_NUMBER]
The default protocol is http. If the atlas.enableTLS property is
set to true, use https. The default HTTP port is 21000 and the
default HTTPS port is 21443. These values can be overridden using the
atlas.server.http.port and
atlas.server.https.port properties, respectively.
-
Stop all running Atlas Metadata Servers.
 | Important |
|---|
You must use the Stop command to stop
the Atlas Metadata Servers. Do not use a Restart command.
This attempts to first stop the newly added Atlas Server, which at this point does
not contain any configurations in /etc/atlas/conf. |
-
In Ambari Web, browse to , then, click Start.
Ambari automatically configures the following Atlas properties in the
/etc/atlas/conf/atlas-application.properties file:
- atlas.server.ids
- atlas.server.address.$id
- atlas.server.ha.enabled
-
To refresh the configuration files, restart the following services that contain
Atlas hooks:
- Hive
- Storm
- Falcon
- Sqoop
- Oozie
-
In Services, browse to .
When you update the Atlas configuration settings in Ambari, Ambari marks the
services that require restart.
-
Browse to , then click Restart All.
Apache Oozie requires a restart after an Atlas configuration update, but may not
be included in the services marked as requiring restart in Ambari.
Review and confirm all recommended configuration changes.
