Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-510 High availability of Atlas
  3. ATLAS-571

Modify Atlas client for necessary changes in context of HA

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.7-incubating
    • None
    • None

    Description

      In ATLAS-511, we are introducing mechanisms to handle automated failover and also redirecting of requests etc. This JIRA is to test and make necessary changes to the AtlasClient class to take advantage of these changes and behave in an optimal manner. This implementation could also serve as a model for others who are writing their own clients against the Atlas API.

      Attachments

        1. ATLAS-571.patch
          85 kB
          Hemanth Yamijala
        2. ATLAS-571-1.patch
          89 kB
          Hemanth Yamijala
        3. ATLAS-571-2.patch
          92 kB
          Hemanth Yamijala
        4. ATLAS-571-3.patch
          92 kB
          Hemanth Yamijala

        Issue Links

          blocks

          Sub-task - The sub-task of the issue ATLAS-572 Handle secure instance of Zookeeper for leader election.

          • Major - Major loss of function.
          • Resolved
          is blocked by

          Sub-task - The sub-task of the issue ATLAS-511 Ability to run multiple instances of Atlas Server with automatic failover to one active server

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue ATLAS-513 Admin support for HA

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Review board link

          Activity

            People

              yhemanth Hemanth Yamijala
              yhemanth Hemanth Yamijala
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: