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

Nick Dimiduk commented on HBASE-12071:
--------------------------------------

{noformat}
--- 
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/RPCProtos.java
+++ 
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/RPCProtos.java
{noformat}

Do not make changes to any generated code. Instead, this comment should be 
updated in hbase-protocol/src/main/protobuf/RPC.proto and the protobuf files 
regenerated.

> 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
>    Affects Versions: 2.0.0
>            Reporter: Sudarshan Kadambi
>            Assignee: Stephen Yuan Jiang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-12071.v2-master.patch, 
> HBASE-12071.v2-master.patch, HBASE-12071.v3-master.patch
>
>
> 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)

Reply via email to