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 C150D200C34 for ; Mon, 27 Feb 2017 11:46:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BFF1A160B6C; Mon, 27 Feb 2017 10:46: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 161BC160B60 for ; Mon, 27 Feb 2017 11:46:07 +0100 (CET) Received: (qmail 13311 invoked by uid 500); 27 Feb 2017 10:46:07 -0000 Mailing-List: contact issues-help@eagle.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@eagle.apache.org Delivered-To: mailing list issues@eagle.apache.org Received: (qmail 13302 invoked by uid 99); 27 Feb 2017 10:46:07 -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; Mon, 27 Feb 2017 10:46:07 +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 DFB5318610E for ; Mon, 27 Feb 2017 10:46:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id GMKQyP2m6ZV1 for ; Mon, 27 Feb 2017 10:46:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8A4065F5F7 for ; Mon, 27 Feb 2017 10:46: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 A8CC7E0A34 for ; Mon, 27 Feb 2017 10:45:46 +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 EB3FD2414E for ; Mon, 27 Feb 2017 10:45:45 +0000 (UTC) Date: Mon, 27 Feb 2017 10:45:45 +0000 (UTC) From: "Hao Chen (JIRA)" To: issues@eagle.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (EAGLE-924) urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 27 Feb 2017 10:46:08 -0000 [ https://issues.apache.org/jira/browse/EAGLE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen reassigned EAGLE-924: ------------------------------ Assignee: Lingang Deng (was: Hao Chen) > urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough > -------------------------------------------------------------------------------------- > > Key: EAGLE-924 > URL: https://issues.apache.org/jira/browse/EAGLE-924 > Project: Eagle > Issue Type: Bug > Components: App::Hadoop JMX Monitor > Affects Versions: v0.5.0 > Reporter: Michael Wu > Assignee: Lingang Deng > Fix For: v0.5.0 > > Attachments: Screen Shot 2017-02-22 at 16.24.09.png > > > Issue: In hbase dashboard of a site, in the top section, there are 2 links referring to urls of healthy and unhealthy region-server lists. But currently, when people click the link, the page is directed to a full list of all region-servers, not the corresponding healthy-list or unhealthy-list. > Suggestion: we can add some filter in the url, for example, append "?status=healthy" or "?status=unhealthy" to the url, and update the link with new urls. > Please see the screenshot in the attachment of this ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)