Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sun, 5 Apr 2015 04:49:34 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12720180.1402341466000.4410.1428209374254@Atlassian.JIRA>
In-Reply-To: <JIRA.12720180.1402341466000@Atlassian.JIRA>
References: <JIRA.12720180.1402341466000@Atlassian.JIRA>
 <JIRA.12720180.1402341466229@arcas>
Subject: [jira] [Updated] (ACCUMULO-2878) Add JMX metrics to Master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser updated ACCUMULO-2878:
---------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.8.0

> Add JMX metrics to Master
> -------------------------
>
>                 Key: ACCUMULO-2878
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2878
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>            Reporter: Josh Elser
>             Fix For: 1.8.0
>
>
> We don't presently have any JMX metrics coming out of the master aside from very low-level statistics on the raw thrift calls.
> The master has loads of really useful high-level information that we would want to track like, alive-tservers/total-tservers, active migrations, offlne tablets, assigned but offline tablets, etc. It could also serve as the centralized view point for "system wide" insight like FATE ops so that each tserver in a system doesn't report information on those.


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