[
https://issues.apache.org/jira/browse/HBASE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977325#comment-13977325
]
Matteo Bertozzi commented on HBASE-11048:
-----------------------------------------
[~jesse_yates] the description is on the document here HBASE-10994.
The idea is to avoid the current N-queues with the "priority" as selector,
because once you give the setPriority() to the client, all the client requests
will be HI priority and that will impact the META requests.
The new scheduler will be also part of the quotas, so each user will get its
own slot and the priority that you set will be reflected inside the user slot,
reordering the user requests.
There will also be another scheduler/queue type where the client will set a
deadline instead of a priority, so you can say I want my query to be executed
in 2sec.
> Support setting custom priority per client RPC
> ----------------------------------------------
>
> Key: HBASE-11048
> URL: https://issues.apache.org/jira/browse/HBASE-11048
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 0.99.0, 0.98.2
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Labels: Phoenix
> Fix For: 0.99.0, 0.98.2
>
> Attachments: hbase-11048-trunk-v0.patch
>
>
> Servers have the ability to handle custom rpc priority levels, but currently
> we are only using it to differentiate META/ROOT updates from replication and
> other 'priority' updates (as specified by annotation tags per RS method).
> However, some clients need the ability to create custom handlers (e.g.
> PHOENIX-938) which can really only be cleanly tied together to requests by
> the request priority. The disconnect is in that there is no way for the
> client to overwrite the priority per table - the PayloadCarryingRpcController
> will always just set priority per ROOT/META and otherwise just use the
> generic priority.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
