[
https://issues.apache.org/jira/browse/HBASE-27355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609504#comment-17609504
]
Duo Zhang commented on HBASE-27355:
-----------------------------------
I've been thinking this for a while recently.
First question, do we really need to give high priority for all requests from
master? For example, the CatalogJanitor, which is a background task, do we
really need to make it high priority? For me I think the answer is no.
So then, the approach of my first comment above is wrong, sorry for doing back
and forth here... I think we still need to go back to your original solution,
i.e, have a special priority and set it in some places where we want the
requests to be high priority.
And there are still several other problems, i.e, how to prevent users set this
priority? The HBaseRpcController interface is IA.LimitedPrivate so probably not
a big problem, but if security is enabled, we could check for system users,
i.e, if it is not admin/system user, we do not allow setting priority greater
than HIGH_QOS. This should be an incompatible change, anyway.
Thanks.
> Separate meta read requests from master and client
> ---------------------------------------------------
>
> Key: HBASE-27355
> URL: https://issues.apache.org/jira/browse/HBASE-27355
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC
> Affects Versions: 3.0.0-alpha-3
> Reporter: ruanhui
> Assignee: ruanhui
> Priority: Minor
> Fix For: 3.0.0-alpha-4
>
>
> If we have a large number of store files in a single region or the response
> from hdfs is slow, the region transition can be slow, the client may put a
> lot of pressure on the meta server when retrying. This may block the master
> system read requests. Maybe we can set a special priority for the master
> request to isolate read requests from master and client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
