[
https://issues.apache.org/jira/browse/HBASE-14239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706053#comment-14706053
]
Elliott Clark edited comment on HBASE-14239 at 8/21/15 1:22 AM:
----------------------------------------------------------------
[~elserj] so the issue comes in that with enough machines on a cluster the
number of report region in transition actions can over whelm the entire
priority threads. That means that the meta movement can be finalized. However
if meta is in transition none of the reportRegionStateTransition calls can
complete until meta is online.
Before HBASE-13351 report region in transition for meta went to the priority
thread all other report region in transition calls went to the default thread
pool ( write pool if RW thread pool was enabled ). HBASE-13351 made it so all
calls to reportRegionStateTransition went to the same pool.
was (Author: eclark):
[~elserj] so the issue comes in that with enough machines on a cluster the
number of report region in transition actions can over whelm the entire
priority threads. That means that non of the meta movements can be finalized.
However if meta is in transition none of the reportRegionStateTransition calls
can complete until meta is online.
Before HBASE-13351 report region in transition for meta went to the priority
thread all other report region in transition calls went to the default thread
pool ( write pool if RW thread pool was enabled ). HBASE-13351 made it so all
calls to reportRegionStateTransition went to the same pool.
> Branch-1.2 AM can get stuck when meta moves
> -------------------------------------------
>
> Key: HBASE-14239
> URL: https://issues.apache.org/jira/browse/HBASE-14239
> Project: HBase
> Issue Type: Sub-task
> Components: Region Assignment
> Affects Versions: 1.2.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 1.2.0
>
> Attachments: HBASE-14239-v1.patch, HBASE-14239.patch
>
>
> When regions are moving master can get totally stuck trying to talk to meta.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
