Hi, Apoorv

What is the main blocker to have multiple Atlas instances all accepting
requests?
Is it the lacking of concurrent transactions support in JanusGraph?  I
understand JanusGraph's concurrent transaction support is rather simple
(compared to ACID) and places requirements on graph schema.

Thanks,

Jerry


On Tue, Nov 20, 2018 at 10:23 AM Apoorv Naik <[email protected]> wrote:

> As of now only ONE instance can be active at a time. Atlas does not have
> the capability to concurrently talk to same JanusGraph across different
> instances.
>
> In this ACTIVE-PASSIVE setup the REST calls will get directed to the active
> instance.
>
> Hope this helps.
>
> *Apoorv Naik*
>
>
> On Tue, Nov 20, 2018 at 10:19 AM abhay kumar <[email protected]>
> wrote:
>
> > Hi,
> > I have been trying to find out about how apache atlas horizontally
> scales.
> > There is no information provided in apache atlas document. Could you
> please
> > help me understand how atlas scales out.
> > 1. Can multiple instances of it deployed on different machines ( all
> > connected to same backend storage e.g. cassandra) and have instances to
> > actively take rest calls for processing ( create/read/update/search types
> > and entities).
> > 2.  Would there be any issue with locking/transaction if all instances
> > process the request ?
> >
> > I understand that the backend storage can be scaled out but I do not know
> > apache atlas process, which uses janusdb, scales out.
> >
> > Thanks & Regards,
> > Abhay
> >
>

Reply via email to