You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Qin Liu (JIRA)" <ji...@apache.org> on 2017/04/13 06:41:41 UTC

[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change

     [ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Qin Liu updated AMBARI-20726:
-----------------------------
    Summary: Aggregate alert does not show status properly at Maintenance Mode change  (was: Aggregate alert does not show status properly after Maintenance Mode change)

> Aggregate alert does not show status properly at Maintenance Mode change
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-20726
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20726
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts
>    Affects Versions: 2.4.2
>            Reporter: Qin Liu
>            Assignee: Qin Liu
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: AMBARI-20726.patch
>
>
> Aggregate alert does not show status properly after Maintenance Mode change.
> Steps to reproduce:
> install a cluster that has HBase with 1 regionserver installed
> Scenario 1
> 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host or on HBase service
> 2. Stop the RegionServer after that
> 3. No red alerts came as expected.
> Percent RegionServers Available - OK affected: [0], total: [1]
> 4. Now Turned Off Maintenance Mode, still kept the Region Server down.
> But Percent RegionServers Available alert still showing "OK"
> Scenario 2:
> 1) Stopped one RegionServer - Red alert seen as expected
> Percent RegionServers Available - CRIT affected: [1], total: [1] 
> 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected
> But Percent RegionServers Available alert showing "CRIT"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)