atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hemanth Yamijala <>
Subject Re: Atlas with hbase/solr/kafka
Date Fri, 22 Jan 2016 06:30:05 GMT
Hi Rishabh,

There are several reasons why we are currently looking at a single *active*
instance of Atlas. The server caches a few types as an optimization. Also,
our current tests show an unlocked version of HBase as backing store for
Titan performs better. Until we find a way around some of these
constraints, it is likely to remain this way.

Please note that we are thinking of supporting an active-passive
arrangement of Atlas with automated failover for a reasonable HA solution.

What is your requirement for multiple *active* instances? Could you please
share your requirements / thoughts?


On Fri, Jan 22, 2016 at 11:50 AM, Rishabh Bhardwaj <>

> Hi,
> I have two instance of atlas (I1,I2) pointing to same hbase/solr/kafka as
> backend.
> When I am creating type/entity something from I1 they are not visible from
> I2.
> I need to restart the I2 to reflect and see the changes.
> Can someone throw some light on this behaviour ? and what is to be done to
> have both the instances (I1 & I2) to be in sync with hbase.
> I read the HA document and it says at present ATLAS can have only one
> active service and in future ATLAS wills support HA for webserive.
> Do we have any JIRA open for above requirement ?
> Thanks,
> Rishabh.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message