Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-2085

In HA deployment, types initialization should be deferred to instance-activation

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.8-incubating
    • 0.8.2, 1.0.0
    • atlas-core
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            madhan Madhan Neethiraj
            madhan Madhan Neethiraj
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment