[
https://issues.apache.org/jira/browse/HBASE-29843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053817#comment-18053817
]
Istvan Toth commented on HBASE-29843:
-------------------------------------
Using setTableName() instead of setPriority(tableName) would not be a problem,
but setting the priority from two places, the overrideable HBaseRpcController
and the fixed ConnectionUtil sounds like trouble.
The final priority would depend on the interaction of the two mechanisms,
leading to hard to debug errors.
IMO having a single mechanism for determining the priority is a much more
robust solution.
> 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)
