You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2014/10/22 12:01:34 UTC

[jira] [Created] (AMBARI-7896) High Availability Ambari Server

Hari Sekhon created AMBARI-7896:
-----------------------------------

             Summary: 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)