You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2017/05/17 16:27:04 UTC
[jira] [Updated] (ATLAS-1675) In HA mode , tag created in Active
Server not present in new Active server after failover.
[ https://issues.apache.org/jira/browse/ATLAS-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhan Neethiraj updated ATLAS-1675:
------------------------------------
Fix Version/s: 0.8.1-incubating
> In HA mode , tag created in Active Server not present in new Active server after failover.
> ------------------------------------------------------------------------------------------
>
> Key: ATLAS-1675
> URL: https://issues.apache.org/jira/browse/ATLAS-1675
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Sharmadha Sainath
> Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1675.patch
>
>
> A)
> 1.host1 , host2 both are up and host1 is ACTIVE.
> 2.Created a tag when host1 is ACTIVE and tag creation is successful .
> 3.Did a manual failover.
> 4.Now host2 is ACTIVE and host1 is PASSIVE.
> *same tag is not present in host2*
> B) :
> 1. host1 is up and host2 is down.
> 2.Created tag in host1 .
> 3.Started host2
> 4.brought down host1 and started host1 (just to make host2 ACTIVE)
> 5.*Now tag is present in host2 and host1*
> This happens only for tag . For entities created through hook or UI , entity persists in both hosts in both scenarios. (Verified with hive_table created through hook and an hdfs_path created in UI)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)