[
https://issues.apache.org/jira/browse/HBASE-29843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053824#comment-18053824
]
Duo Zhang commented on HBASE-29843:
-----------------------------------
Or maybe we can change the interface like this
1. Introduce a new method setPriority(int, TableName) to HBaseRpcController,
the default implementation is to call setPriority(int) and then call
setPriority(TableName)
2. Mark setPriority(int) and setPriority(TableName) both deprecated.
3. In the default implementation of HBaseRpcController, we use the rules
introduced in my above comment.
WDYT?
Thanks.
> HBaseRPCController.setPriority(final TableName tn) is never called on
> branch-3+
> -------------------------------------------------------------------------------
>
> Key: HBASE-29843
> URL: https://issues.apache.org/jira/browse/HBASE-29843
> Project: HBase
> Issue Type: Bug
> Components: rpc
> Affects Versions: 3.0.0-beta-1
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> HBaseRPCController makes it possible to set the priority based on the table
> name of an operation.
> This has stopped working on branch-3+.
> It is set at
> [https://github.com/apache/hbase/blob/8c69ba12f6daf853e4bd5ee78ab01a6f1a88eb89/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RegionServerCallable.java#L122]
> on branch-2, but it is never called on branch-3 + .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
