hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12071) Separate out thread pool for Master <-> RegionServer communication
Date Tue, 30 Sep 2014 23:56:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154050#comment-14154050
] 

Andrew Purtell commented on HBASE-12071:
----------------------------------------

Regarding HBASE-12028, I'd say we should abort the RS if a handler thread terminates due to
an unhandled throwable, and if so we wouldn't need this. However

bq. This addresses [...] but also long-running queries or co-processor executions holding
up master operations.

True. 


> 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)

Mime
View raw message