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

Hadoop QA commented on HBASE-12071:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12689893/HBASE-12071.v2-master.patch
  against master branch at commit 820f629423f21fbd1dcc7a383955443a2595fd5d.
  ATTACHMENT ID: 12689893

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/12292//console

This message is automatically generated.

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