[
https://issues.apache.org/jira/browse/AMBARI-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258765#comment-15258765
]
Intekhab Choudhury commented on AMBARI-7896:
--------------------------------------------
As stated above, for HA
-Both servers should point to the same database (external to Ambari Server) .
Preferably Server.jdbc.hostname should point to a HA DB Cluster from both
server's ambari.properties.
-Load Balancer (preferably an external solution, like F5, Cisco, Brocade etc)
to create VIP and use the Ambari server as Real to direct traffic to either
host rather than keeping one as Standby (Agent ini file should point to DNS of
VIP rather than to a server directly)
> High Availability Ambari Server
> -------------------------------
>
> Key: AMBARI-7896
> URL: https://issues.apache.org/jira/browse/AMBARI-7896
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Environment: HDP 2.1
> Reporter: Hari Sekhon
>
> Ambari server needs high availability as loss of the Ambari server machine
> would leave it's cluster unmanageable.
> This could reuse ZooKeeper for Active/Standby election. I'm not sure if it's
> practical in scalability terms to store the configurations in ZK for
> management of larger clusters, perhaps that could use HA databases such as
> MySQL multi-master or replicate the config itself at the application layer to
> the standby Ambari server.
> Right now I guess you can roll your own with Linux HA + DRBD but it feels
> like this should be native as per other components that leverage ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
