[
https://issues.apache.org/jira/browse/HBASE-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909532#action_12909532
]
ryan rawson commented on HBASE-2782:
------------------------------------
Where else would QoSFunction go? It has to know intimate details about the
regionserver, in order to discern if a scan belongs to a META table or not.
I tweaked the queue size per handler so that i would have less blocking,
although I'm not sure how good of an idea this is. I can revert on commit.
There are only 2 API changes:
- Add new parameters for high priority RPC pools and levels
- Add new setter for QosFunction
that is about it IIRC... its all internal elsewise?
> QOS for META table access
> -------------------------
>
> Key: HBASE-2782
> URL: https://issues.apache.org/jira/browse/HBASE-2782
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.89.20100621
> Reporter: Todd Lipcon
> Assignee: ryan rawson
> Fix For: 0.90.0
>
> Attachments: HBASE-2782.txt
>
>
> I'd like to brainstorm some ideas on how we can prioritize reads and writes
> to META above reads and writes to other tables. I've noticed that if the
> regionserver hosting META is under heavy load, then lots of other operations
> take much longer than they should. For example, I'm currently running 120
> threads of YCSB across 3 client nodes hitting a 5-node cluster. Doing a full
> scan of META (only 600 rows) takes upwards of 30 seconds in the shell, since
> all of the handler threads are tied up and there's a long RPC queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
