[
https://issues.apache.org/jira/browse/HBASE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198801#comment-15198801
]
Hudson commented on HBASE-15470:
--------------------------------
FAILURE: Integrated in HBase-Trunk_matrix #782 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/782/])
HBASE-15470 Add a setting for Priority queue length (eclark: rev
ac1a7a4a78966826d755a21faa007f9ae03f2cd0)
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcExecutor.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcScheduler.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/FifoRpcScheduler.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java
> Add a setting for Priority queue length
> ---------------------------------------
>
> Key: HBASE-15470
> URL: https://issues.apache.org/jira/browse/HBASE-15470
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC, Region Assignment
> Affects Versions: 1.2.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-15470.patch
>
>
> Meta can have very different request rates than any other region. We
> shouldn't use the same call queue length.
> For example:
> If a normal request takes 100ms ( long scan or large get )
> but a call to meta is all in memory so it takes < 1ms
> So a call queue length of 100 represents multiple seconds of work for normal
> requests, but less than a second for meta.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
