[
https://issues.apache.org/jira/browse/ATLAS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231391#comment-15231391
]
Hemanth Yamijala commented on ATLAS-603:
----------------------------------------
bq. 1. I see that the known issue for
https://issues.apache.org/jira/browse/ATLAS-338 has been removed but dont see
it fixed.
I will resolve this. This was resolved with ATLAS-512. Now that we don't have a
call to check model registration from hive hook, it should not be a problem. I
can test this once later today and update.
bq. 2. It would be good to relook at Hbase region server HA and see if the
behaviour has changed in the newer versions and see if we can enable that?
I can have a word with HBase committers. But it doesn't seem like there's any
change. The latest docs on this are still here:
http://hortonworks.com/blog/apache-hbase-high-availability-next-level/. And the
JIRA it links to for enhancements - HBASE-12259 is still open.
> Document High Availability of Atlas
> -----------------------------------
>
> Key: ATLAS-603
> URL: https://issues.apache.org/jira/browse/ATLAS-603
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Attachments: ATLAS-603.patch
>
>
> The document:
> * Mechanism
> * Config items
> * Client changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
