Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1805801660.1206990144799.JavaMail.jira@brutus>
Date: Mon, 31 Mar 2008 12:02:24 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-543) A region's state is kept in several
 places in the master opening the possibility for race conditions
In-Reply-To: <110325218.1206397644432.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jim Kellerman updated HBASE-543:
--------------------------------

    Description: 
A region's state exists in multiple maps in the RegionManager: unassignedRegions, pendingRegions, regionsToClose, closingRegions, regionsToDelete, etc.

One of these race conditions was found in HBASE-534.

For HBase-0.1.x, we should just patch the holes we find.

The ultimate solution (which requires a lot of changes in HMaster) should be applied to HBase trunk.

Proposed solution:

Create a class that encapsulates a region's state and provide synchronized access to the class that validates state changes.
There should be a single structure that holds regions in these transitional states and it should be a synchronized collection of some kind.


  was:
A region's state exists in multiple maps in the RegionManager: unassignedRegions, pendingRegions, regionsToClose, closingRegions, regionsToDelete, etc.

One of these race conditions was found in HBASE-534.

Proposed solution:

Create a class that encapsulates a region's state and provide synchronized access to the class that validates state changes.
There should be a single structure that holds regions in these transitional states and it should be a synchronized collection of some kind.


> A region's state is kept in several places in the master opening the possibility for race conditions
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-543
>                 URL: https://issues.apache.org/jira/browse/HBASE-543
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.2.0, 0.1.1, 0.1.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.2.0, 0.1.1
>
>
> A region's state exists in multiple maps in the RegionManager: unassignedRegions, pendingRegions, regionsToClose, closingRegions, regionsToDelete, etc.
> One of these race conditions was found in HBASE-534.
> For HBase-0.1.x, we should just patch the holes we find.
> The ultimate solution (which requires a lot of changes in HMaster) should be applied to HBase trunk.
> Proposed solution:
> Create a class that encapsulates a region's state and provide synchronized access to the class that validates state changes.
> There should be a single structure that holds regions in these transitional states and it should be a synchronized collection of some kind.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.