Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 60C5E200C73 for ; Wed, 10 May 2017 23:05:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5F7E2160BB4; Wed, 10 May 2017 21:05:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A36BD160BC6 for ; Wed, 10 May 2017 23:05:07 +0200 (CEST) Received: (qmail 2212 invoked by uid 500); 10 May 2017 21:05:06 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 2202 invoked by uid 99); 10 May 2017 21:05:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2017 21:05:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 809661813ED for ; Wed, 10 May 2017 21:05:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id CiI5DyMVcdfr for ; Wed, 10 May 2017 21:05:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 450255FC4D for ; Wed, 10 May 2017 21:05:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C21D1E0C0D for ; Wed, 10 May 2017 21:05:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 294F121E0D for ; Wed, 10 May 2017 21:05:04 +0000 (UTC) Date: Wed, 10 May 2017 21:05:04 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 10 May 2017 21:05:08 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20726: ------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > 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 at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. > Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. > But Percent RegionServers Available alert will still show "OK" - "CRIT" is expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. > But Percent RegionServers Available alert will still show "CRIT" - "OK" is expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)