You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrey Stepachev (JIRA)" <ji...@apache.org> on 2015/01/20 13:31:34 UTC
[jira] [Commented] (HBASE-12880) RegionState in state SPLIT doesn't
removed from region states
[ https://issues.apache.org/jira/browse/HBASE-12880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283773#comment-14283773 ]
Andrey Stepachev commented on HBASE-12880:
------------------------------------------
Checked more carefully. It seem that offlined SPLIT regions never removed from region states. Merged regions are the same here.
It seems those regions should be deleted entirely upon Offlined event.
> RegionState in state SPLIT doesn't removed from region states
> -------------------------------------------------------------
>
> Key: HBASE-12880
> URL: https://issues.apache.org/jira/browse/HBASE-12880
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Andrey Stepachev
> Attachments: master-with-split-regions-2-1.jpg
>
>
> During my work on patch HBASE-7332 I stumbled on strange behaviour in RegionStates. Split region doesn't removed from regionStates in regionOffline() method and RegionState for this region sits in regionStates map indefinitely long (until RS rebooted).
> (that is clearly seen in HBASE-7332 by simple creating table and splitting it from command line).
> Is that was intended to be so and some chore eventually will remove it from regionStates (didn't find with fast code scanning) or here can be resource leak?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)