You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Alicia Ying Shu (JIRA)" <ji...@apache.org> on 2016/02/09 00:37:40 UTC

[jira] [Assigned] (HBASE-14358) Parent region is not removed from regionstates after a successful split

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

Alicia Ying Shu reassigned HBASE-14358:
---------------------------------------

    Assignee: Alicia Ying Shu

> Parent region is not removed from regionstates after a successful split
> -----------------------------------------------------------------------
>
>                 Key: HBASE-14358
>                 URL: https://issues.apache.org/jira/browse/HBASE-14358
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.1, 1.0.3, 1.1.3
>            Reporter: Esteban Gutierrez
>            Assignee: Alicia Ying Shu
>            Priority: Critical
>
> Ran into this while trying to find out why region_mover.rb was not catching an exception after a region was split. Digging further I found that the problem is happening in the handling of the region state in the Master since we don't remove the old state after the split is successful:
> {code}
> 2015-09-03 02:56:49,255 INFO org.apache.hadoop.hbase.master.AssignmentManager: Ignored moving region not assigned: {ENCODED => 9a4930ed41dc7013d9956240e6f5c03e, NAME => 'u,user3605,1432797255754.9a4930ed41dc7013d9956240e6f5c03e.', STARTKEY => 'user3605', ENDKEY => 'user3723'}, {9a4930ed41dc7013d9956240e6f5c03e state=SPLIT, ts=1441273152561, server=a2209.halxg.cloudera.com,22101,1441243232790}
> {code}
> I don't think the problem is happening in the master branch but at least I've been able to confirm this is happening on branch-1 and branch-1.2 at least.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)