[
https://issues.apache.org/jira/browse/ATLAS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372488#comment-15372488
]
ATLAS QA commented on ATLAS-998:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12817338/ATLAS-998.patch
against master revision e13fa5e.
{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:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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 381 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 :
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Test results:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsplugin-classloader.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/397//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/397//console
This message is automatically generated.
> Atlas should determine HA mode from property atlas.server.ids, instead of
> atlas.server.ha.enabled
> -------------------------------------------------------------------------------------------------
>
> Key: ATLAS-998
> URL: https://issues.apache.org/jira/browse/ATLAS-998
> Project: Atlas
> Issue Type: Bug
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Attachments: ATLAS-998.patch
>
>
> Atlas server uses the value of property 'atlas.server.ha.enabled' to
> determine if Atlas is running in High-Available mode or not. Another property
> 'atlas.server.ids' lists all the server instances configured to run in the
> cluster. This and other related properties are used to determine if a server
> should be run in active or pass mode.
> Instead of using 2 different properties, Atlas can determine if HA mode is
> enabled or not by looking at the number of instances listed in
> 'atlas.server.ids' property. When multiple instances are listed in this
> property, Atlas will run in HA mode; else it will run in stand-alone mode.
> Using a single property might be less confusing to manage and troubleshoot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
