[
https://issues.apache.org/jira/browse/HBASE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243672#comment-14243672
]
Stephen Yuan Jiang commented on HBASE-12071:
--------------------------------------------
[~apurtell] currently we have 3 RpcExecutor for different request types:
- priorityExecutor for meta table request and some admin requests
- replicationExecutor for replication requests
- callExecutor for normal requests.
Each executor used different thread pools. This should be enough to address
[~skadambi]'s concern.
I went through the Admin.proto and could add more admin requests (master <->
region server communication) to use priorityExecutor.
> Separate out thread pool for Master <-> RegionServer communication
> ------------------------------------------------------------------
>
> Key: HBASE-12071
> URL: https://issues.apache.org/jira/browse/HBASE-12071
> Project: HBase
> Issue Type: Improvement
> Reporter: Sudarshan Kadambi
> Assignee: Stephen Yuan Jiang
>
> Over in HBASE-12028, there is a discussion about the case of a RegionServer
> still being alive despite all its handler threads being dead. One outcome of
> this is that the Master is left hanging on the RS for completion of various
> operations - such as region un-assignment when a table is disabled. Does it
> make sense to create a separate thread pool for communication between the
> Master and the RS? This addresses not just the case of the RPC handler
> threads terminating but also long-running queries or co-processor executions
> holding up master operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
