hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15470) Add a setting for Priority queue length
Date Thu, 17 Mar 2016 06:04:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198806#comment-15198806
] 

Hudson commented on HBASE-15470:
--------------------------------

FAILURE: Integrated in HBase-1.4 #24 (See [https://builds.apache.org/job/HBase-1.4/24/])
HBASE-15470 Add a setting for Priority queue length (eclark: rev f1bb26c2235e231c6326cd5c78932f492844b8aa)
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcScheduler.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcExecutor.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/FifoRpcScheduler.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)

Mime
View raw message