You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2017/07/01 01:00:02 UTC
[jira] [Commented] (HBASE-15816) Provide client with ability to set
priority on Operations
[ https://issues.apache.org/jira/browse/HBASE-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070916#comment-16070916 ]
Duo Zhang commented on HBASE-15816:
-----------------------------------
I'm OK with exposing priority to user.
The only concern is that we need to make sure that our RpcServer implementation will not crash if user sets a strange priority, for example, a negative value, or Integer.MAX_VALUE?
And Should we normalize the priority value that exposes to user? For example, only 0-10 or 0-100?
Thanks.
> 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.patch, HBASE-15816-v1.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.4.14#64029)