[
https://issues.apache.org/jira/browse/HBASE-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508499#comment-14508499
]
Lars Hofhansl commented on HBASE-13420:
---------------------------------------
OH, I see, misunderstood, sorry.
Reading back in the thread... I don't see the queue could lock up a thread for
20s at a time, unless we have some pathologically unfair scheduling case. I
think in the description we mean the total time spent in this, right?
Patch is fine. Introducing a new class just for this seems a bit heavy weight,
on the other hand I do not see an alternative.
> RegionEnvironment.offerExecutionLatency Blocks Threads under Heavy Load
> -----------------------------------------------------------------------
>
> Key: HBASE-13420
> URL: https://issues.apache.org/jira/browse/HBASE-13420
> Project: HBase
> Issue Type: Improvement
> Reporter: John Leach
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.1.0, 0.98.13, 1.0.2
>
> Attachments: 1M-0.98.12.svg, 1M-0.98.13-SNAPSHOT.svg,
> HBASE-13420.patch, HBASE-13420.txt, hbase-13420.tar.gz,
> offerExecutionLatency.tiff
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> The ArrayBlockingQueue blocks threads for 20s during a performance run
> focusing on creating numerous small scans.
> I see a buffer size of (100)
> private final BlockingQueue<Long> coprocessorTimeNanos = new
> ArrayBlockingQueue<Long>(
> LATENCY_BUFFER_SIZE);
> and then I see a drain coming from
> MetricsRegionWrapperImpl with 45 second executor
> HRegionMetricsWrapperRunable
> RegionCoprocessorHost#getCoprocessorExecutionStatistics()
> RegionCoprocessorHost#getExecutionLatenciesNanos()
> Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
