You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sudarshan Kadambi (JIRA)" <ji...@apache.org> on 2014/09/23 22:50:34 UTC

[jira] [Created] (HBASE-12071) Separate out thread pool for Master <-> RegionServer communication

Sudarshan Kadambi created HBASE-12071:
-----------------------------------------

             Summary: Separate out thread pool for Master <-> RegionServer communication
                 Key: HBASE-12071
                 URL: https://issues.apache.org/jira/browse/HBASE-12071
             Project: HBase
          Issue Type: Bug
            Reporter: Sudarshan Kadambi


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)