hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Yuan Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12071) Separate out thread pool for Master <-> RegionServer communication
Date Tue, 06 Jan 2015 17:00:38 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephen Yuan Jiang updated HBASE-12071:
---------------------------------------
    Fix Version/s: 1.1.0

> 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, 1.1.0
>            Reporter: Sudarshan Kadambi
>            Assignee: Stephen Yuan Jiang
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-12071.v1-branch-1.patch, HBASE-12071.v2-master.patch, HBASE-12071.v2-master.patch,
HBASE-12071.v3-master.patch, HBASE-12071.v4-master.patch, HBASE-12071.v5-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)

Mime
View raw message