[jira] [Resolved] (HBASE-18848) meta region loading reporter

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

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

Andrew Kyle Purtell resolved HBASE-18848.
-----------------------------------------
    Resolution: Duplicate

This is effectively duplicated by later work on meta metrics. 

> 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: Michael Stack
>            Priority: Major
>              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
(v8.20.7#820007)