Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 19 Sep 2017 17:20:00 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13103297.1505841515000.148922.1505841600325@Atlassian.JIRA>
In-Reply-To: <JIRA.13103297.1505841515000@Atlassian.JIRA>
References: <JIRA.13103297.1505841515000@Atlassian.JIRA> <JIRA.13103297.1505841515512@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18848) meta region loading reporter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Sep 2017 17:20:04 -0000


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

stack updated HBASE-18848:
--------------------------
           Tags: beginner
         Labels: beginner  (was: )
    Component/s: tooling
                 Operability

> meta region loading reporter
> ----------------------------
>
>                 Key: HBASE-18848
>                 URL: https://issues.apache.org/jira/browse/HBASE-18848
>             Project: HBase
>          Issue Type: Bug
>          Components: Operability, tooling
>            Reporter: stack
>              Labels: beginner
>
> We need reporting on meta table accesses.
> In quiet a few cases, it is said that our client -- I can believe it -- does too many lookups against meta.
> In another case, we found that the hbase canary was ddos'ing the meta table but it took a bunch of messing digging in rpc TRACE to figure out this was the case.
> A few users at scale are fingering meta ops as the bound to their being able to scale more (especially if their readers are hosted in MR and startup is a big bang burst of meta scanning)
> The report would dump numbers on clients, incidence and type of queries. It would highlight bad actors and pathological behaviors.
> This is a particular instance of what a general trace system might provide but we don't have that yet. This could be a good first exercise implementing a trace or it might just use trace engine mechanics to realize a few dump jsps. Whatever, we need some tooling for operators.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)