atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <>
Subject [jira] [Assigned] (ATLAS-511) Ability to run multiple instances of Atlas Server with automatic failover to one active server
Date Tue, 01 Mar 2016 05:03:18 GMT


Hemanth Yamijala reassigned ATLAS-511:

    Assignee: Hemanth Yamijala

> Ability to run multiple instances of Atlas Server with automatic failover to one active
> ----------------------------------------------------------------------------------------------
>                 Key: ATLAS-511
>                 URL:
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
> One of the most important components that only supports active-standby mode currently
is the Atlas server which hosts the API / UI for Atlas. As described in the [HA Documentation|],
we currently are limited to running only one instance of the Atlas server behind a proxy service.
If the running instance goes down, a manual process is required to bring up another instance.
> In this JIRA, we propose to have an ability to run multiple Atlas server instances. However,
as a first step, only one of them will be actively processing requests. To have a consistent
terminology, let us call that server the *master*. Any requests sent to the other servers
will be redirected to the master.
> When the master suffers a partition, one of the other servers must automatically become
the master and start processing requests. What this mode brings us over the current system
is the ability to automatically failover the Atlas server instance without any  manual intervention.
Note that this can be arguably called an [active/active setup|]
> ATLAS-488 raised to support multiple active Atlas server instances. While that would
be ideal, we have to learn more about the underlying system behavior before we can get there,
and hopefully we can take smaller steps to improve the system systematically. The method proposed
here is similar to what is adopted in many other Hadoop components including HDFS NameNode,
HBase HMaster etc.

This message was sent by Atlassian JIRA

View raw message