[
https://issues.apache.org/jira/browse/HBASE-27355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614716#comment-17614716
]
ruanhui commented on HBASE-27355:
---------------------------------
Hi Duo
Do you think we can use an additional RpcExecutor to specifically serve all
internal system table requests ?
Not only the master, the regionservers also accesses the system tables, like
hbase:quota and hbase:replication. So if clients retry a lot, the replication
maybe be blocked too(if we deploy hbase:meta and hbase:replication on same
regionserver, which is common in our production to using a specific rsgroup to
hold all system tables). Based on this consideration, is it better to seperate
intenal requests (both from masters and regionservers, including the requests
from CatalogJanitor) and client requests ?
> 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)
