[
https://issues.apache.org/jira/browse/AMBARI-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623311#comment-14623311
]
Scott Edwards commented on AMBARI-7896:
---------------------------------------
I would also like to see a robust HA solution for Ambari. As the manager of a
highly available system, Ambari should also itself be highly available. The
only option I see right now is to restore Ambari's DB on a new host per this
guidance:
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.3.2/bk_using_Ambari_book/content/ambari-chap11.html
> 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)
