[
https://issues.apache.org/jira/browse/HBASE-27355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600126#comment-17600126
]
Duo Zhang commented on HBASE-27355:
-----------------------------------
So the solution here is to have a special handler group for handling meta
requests from master only?
Is it possible to not expose another QOS number in HConstants? Could we just
check whether the requests are coming from master and give it a high prority
automatically?
> 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)
