[
https://issues.apache.org/jira/browse/HBASE-11048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977540#comment-13977540
]
Jesse Yates commented on HBASE-11048:
-------------------------------------
[~mbertozzi] I think what I'm doing with making the payload rpc controller
pluggable actually makes the following:
{quote}
because once you give the setPriority() to the client, all the client requests
will be HI priority and that will impact the META requests.
{quote}
less of an issue as it allows the client to plug in their own implementation,
which could be a one smarter about which table gets which priority (so meta,
root keep their high priority and other tables can be ordered on priority).
Clearly, this is well short of what you are proposing, but maybe its a good
intermediate step? Maybe it might save you some small amount of work?
For phoenix, we are creating an HTable on the server side to write between RS
for the mutable secondary indexes. So the priority is somewhat surfaced to
client (ala config values), but not actually changing the API.
I'm not sure how [~apurtell] feels about your work going into 0.98, so this
issue might be the way forward for that until you finish up the work for trunk?
Just trying to figure out how we can all eat our cake :)
> 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)
