[jira] [Commented] (HBASE-15816) Provide client with ability to set priority on Operations

["Clay B. (JIRA)" <ji...@apache.org>]

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

Clay B. commented on HBASE-15816:
---------------------------------

[~churromorales] This is very cool!

My only challenge is in groking as an operator a misbehaved client or the pain of debugging SLA misses trying to use this. (Maybe not the feature for my perceived problem?) Would it be imprudent to add a JMX metric for priority requests per table (or region) so one could see if a client is asking for ADMIN_QOS on all their requests or some silliness?

> Provide client with ability to set priority on Operations 
> ----------------------------------------------------------
>
>                 Key: HBASE-15816
>                 URL: https://issues.apache.org/jira/browse/HBASE-15816
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: churro morales
>            Assignee: churro morales
>         Attachments: HBASE-15816-v1.patch, HBASE-15816.patch
>
>
> First round will just be to expose the ability to set priorities for client operations.  For more background: http://mail-archives.apache.org/mod_mbox/hbase-dev/201604.mbox/%3CCA+RK=_BG_o=q8HMptcP2WauAinmEsL+15f3YEJuz=qbpcya5-g@mail.gmail.com%3E
> Next step would be to remove AnnotationReadingPriorityFunction and have the client send priorities explicitly.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)