[
https://issues.apache.org/jira/browse/HBASE-15134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475713#comment-15475713
]
Sean Busbey commented on HBASE-15134:
-------------------------------------
Thanks for your work on this so far!
we should avoid needing synchronization unless we need it for correctness.
generally, an approximation should be fine for metrics like this.
in the future, please use `git format-patch` to create your patches, so we get
a commit message and your preferred authorship line. For more details on this,
and pointers to some helper scripts see [the ref guide section on submitting
patches|http://hbase.apache.org/book.html#submitting.patches]
> Add visibility into Flush and Compaction queues
> -----------------------------------------------
>
> Key: HBASE-15134
> URL: https://issues.apache.org/jira/browse/HBASE-15134
> Project: HBase
> Issue Type: New Feature
> Components: Compaction, metrics, regionserver
> Reporter: Elliott Clark
> Assignee: Abhishek Singh Chouhan
> Attachments: HBASE-15134.patch, HBASE-15134.patch
>
>
> On busy spurts we can see regionservers start to see large queues for
> compaction. It's really hard to tell if the server is queueing a lot of
> compactions for the same region, lots of compactions for lots of regions, or
> just falling behind.
> For flushes much the same. There can be flushes in queue that aren't being
> run because of delayed flushes. There's no way to know from the metrics how
> many flushes are for each region, how many are delayed. Etc.
> We should add either more metrics around this ( num per region, max per
> region, min per region ) or add on a UI page that has the list of compactions
> and flushes.
> Or both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
