[
https://issues.apache.org/jira/browse/ATLAS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-510.
------------------------------------
Resolution: Done
> High availability of Atlas
> --------------------------
>
> Key: ATLAS-510
> URL: https://issues.apache.org/jira/browse/ATLAS-510
> Project: Atlas
> Issue Type: New Feature
> Reporter: Hemanth Yamijala
> Priority: Major
>
> There has been some work done at various levels to improve availability of
> Atlas. Architecturally, using highly available dependent components like
> HBase, Solr and Kafka allows Atlas to rely on the HA capabilities of these
> components (like replicas) to ensure it is not impacted by single machine
> failures. Integrating components (like Hive, Sqoop, Falcon, Storm) use Kafka
> to integrate with Atlas. In principle, this allows the integrating components
> to not be impacted due to loss of connectivity with Atlas while ensuring no
> loss of data.
> However, there are still some important changes that the system requires for
> improving availability guarantees of Atlas. This JIRA is a master JIRA to
> track this work. I expect to open several child JIRAs to elaborate on the
> tasks and make it more manageable from a development / review perspective.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
