[ https://issues.apache.org/jira/browse/ATLAS-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197516#comment-15197516 ]
ATLAS QA commented on ATLAS-511: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12793729/ATLAS-511-1.patch against master revision ad0d764. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 7 new or modified test files. {color:red}-1 javac{color}. The applied patch generated 102 javac compiler warnings (more than the master's current 98 warnings). {color:green}+1 javadoc{color}. There were no new javadoc warning messages. +1 checkstyle. The patch generated 0 code style errors. {color:red}-1 findbugs{color}. The patch appears to introduce 339 new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in : ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT ./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT ./webapp/target/failsafe-reports/TEST-org.apache.atlas.web.resources.HiveLineageJerseyResourceIT ./webapp/target/failsafe-reports/junitreports/TEST-org.apache.atlas.web.resources.HiveLineageJerseyResourceIT Test results: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningsrepository.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningscommon.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningsnotification.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningswebapp.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningsclient.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html Findbugs warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/newPatchFindbugsWarningstitan.html Javac warnings: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//artifact/patchprocess/diffJavacWarnings.txt Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/76//console This message is automatically generated. > Ability to run multiple instances of Atlas Server with automatic failover to > one active server > ---------------------------------------------------------------------------------------------- > > Key: ATLAS-511 > URL: https://issues.apache.org/jira/browse/ATLAS-511 > Project: Atlas > Issue Type: Sub-task > Reporter: Hemanth Yamijala > Assignee: Hemanth Yamijala > Attachments: ATLAS-511-1.patch, ATLAS-511.patch, HADesign.pdf > > > One of the most important components that only supports active-standby mode > currently is the Atlas server which hosts the API / UI for Atlas. As > described in the [HA > Documentation|http://atlas.incubator.apache.org/0.6.0-incubating/HighAvailability.html], > we currently are limited to running only one instance of the Atlas server > behind a proxy service. If the running instance goes down, a manual process > is required to bring up another instance. > In this JIRA, we propose to have an ability to run multiple Atlas server > instances. However, as a first step, only one of them will be actively > processing requests. To have a consistent terminology, let us call that > server the *master*. Any requests sent to the other servers will be > redirected to the master. > When the master suffers a partition, one of the other servers must > automatically become the master and start processing requests. What this mode > brings us over the current system is the ability to automatically failover > the Atlas server instance without any manual intervention. Note that this > can be arguably called an [active/active > setup|https://en.wikipedia.org/wiki/High-availability_cluster] > ATLAS-488 raised to support multiple active Atlas server instances. While > that would be ideal, we have to learn more about the underlying system > behavior before we can get there, and hopefully we can take smaller steps to > improve the system systematically. The method proposed here is similar to > what is adopted in many other Hadoop components including HDFS NameNode, > HBase HMaster etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)