ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14719) After enabling NN HA AMS shows critical alert
Date Tue, 19 Jan 2016 16:41:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106975#comment-15106975
] 

Hadoop QA commented on AMBARI-14719:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12783101/AMBARI-14719.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 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 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-web 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4970//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4970//console

This message is automatically generated.

> After enabling NN HA AMS shows critical alert
> ---------------------------------------------
>
>                 Key: AMBARI-14719
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14719
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.1
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Blocker
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14719.patch, AMBARI-14719_branch_2.2.patch
>
>
> 1. deploy cluster with few services
> 2. Enable NN HA
> 3. stop ambari metrics
> 4. Update configs:
> "Metrics Service operation mode" :"distributed"
> "hbase.cluster.distributed": "true"
> "hbase.rootdir": "hdfs://nameservice/amshbase"
> 5. restart ambari metrcis
> Expected: ambari metrics is up and running and no alerts should be present
> Actual: 1 critical alert present on metrics
> NOTE: test might have also enabled security after teh above mentioneds teps but teh metrics
alert starts showing up after NN HA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message