atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-2085) In HA deployment, types initialization should be deferred to instance-activation
Date Thu, 24 Aug 2017 18:58:00 GMT

     [ https://issues.apache.org/jira/browse/ATLAS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Madhan Neethiraj updated ATLAS-2085:
------------------------------------
    Attachment: ATLAS-2085.2.patch

> In HA deployment, types initialization should be deferred to instance-activation
> --------------------------------------------------------------------------------
>
>                 Key: ATLAS-2085
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2085
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.8-incubating
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>             Fix For: 0.9-incubating
>
>         Attachments: ATLAS-2085.2.patch
>
>
> In HA deployments Atlas instances load bootstrap types during initialization i.e. before
leader election. When Atlas is brought up for the first time, this will initialize the store
with the types defined in the model files.
> Index setup kicks in when an instance is activated - GraphBackedSearchIndexer.initialize();
this looks for a specific property name ('__type') in graph management and upon finding it,
Atlas skips rest of the initialization (creation of indexes like vertex_index, edge_index,
fulltext_index). This results in subsequent queries to fail with error "vertex_index" not
found.
> The fix is to defer loading of bootstrap types to instance-activation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message