[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789571#comment-16789571 ] Shubham Srivastava commented on AMBARI-17126: - Has this moved towards closure? > 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 >Priority: Major > 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 (v7.6.3#76005)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272885#comment-16272885 ] Hari Sekhon commented on AMBARI-17126: -- Any movement on this guys? I raised AMBARI-7896 for Ambari HA more than 3 years ago... > 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.4.14#64029)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[
https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623099#comment-15623099 ] Edward Mangini commented on AMBARI-17126: - I have two questions: 1.) Is this actively being looked at for 2.5? (Is there an estimated release date for 2.5?) 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. > 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: 2.5.0 > > > 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)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385935#comment-15385935 ] Benjamin Ruland commented on AMBARI-17126: -- [~bergenholtz] Can you explain, how this is already possible today? Do you refer to an active-active setup with both Ambari's configured exactly the same way and accessible via a load-balancer? > 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 > Fix For: 2.5.0 > > > 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)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373634#comment-15373634 ] Erik Bergenholtz commented on AMBARI-17126: --- It seems the above describes something that is already possible with capabilities available today in Ambari. It would be desirable to entertain capabilities in Ambari that allow for native functionality that would use [something like] ZK leader election as described in AMBARI-7896. > 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 > Fix For: 2.5.0 > > > 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)
