[
https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623872#comment-15623872
]
Swapan Shridhar commented on AMBARI-17126:
------------------------------------------
[~allmusic76]
{quote}
1.) Is this actively being looked at for 2.5? (Is there an estimated release
date for 2.5?)
{quote}
- It is not for Ambari-2.5.
{quote}
2.) Also, why exactly was AMBARI-7896 closed and being tracked here?
Active-Passive fault tolerance/redundancy isn't necessarily the same concept as
high availability.
{quote}
Here also, we are working on having one Ambari server active at one point of
time and other passive/non-active, and we are not doing the load balancing part
as part of this JIRA.
> Provide Ambari Server HA (active-passive)
> -----------------------------------------
>
> Key: AMBARI-17126
> URL: https://issues.apache.org/jira/browse/AMBARI-17126
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Jeff Sposetti
> Assignee: Swapan Shridhar
> Fix For: trunk
>
>
> Ability to configure Ambari Server active-passive setup behind Load balancer.
> -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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
