[
https://issues.apache.org/jira/browse/HBASE-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909544#action_12909544
]
Todd Lipcon commented on HBASE-2782:
------------------------------------
Yea, -1 on increasing the queue size - those calls can eat a lot of memory, eg
if they're bulk puts.
Over in Hadoop land they solved the pooling issue by having the NN listen on
multiple ports, where each port is dedicated to a different "priority level".
It's sort of nice since you can do network-level QoS as well to help things
out, plus you don't have the issue of having to read a call in order to know if
it's high priority. The downside of course is that you expose many more ports.
Thoughts?
> 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.
