hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11048) Support setting custom priority per client RPC
Date Thu, 22 May 2014 20:39:06 GMT

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

Jesse Yates commented on HBASE-11048:
-------------------------------------

Thanks for taking a look [~apurtell]! I'll commit this evening (right under the RC deadline
:)), unless there are any objections 

> 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.3
>
>         Attachments: hbase-11048-0.98-v0.patch, hbase-11048-trunk-v0.patch, hbase-11048-trunk-v1.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)

Mime
View raw message