You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/09/19 17:19:00 UTC
[jira] [Created] (HBASE-18848) meta region loading reporter
stack created HBASE-18848:
-----------------------------
Summary: meta region loading reporter
Key: HBASE-18848
URL: https://issues.apache.org/jira/browse/HBASE-18848
Project: HBase
Issue Type: Bug
Reporter: stack
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)