Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <741420.1187994930658.JavaMail.jira@brutus>
Date: Fri, 24 Aug 2007 15:35:30 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1780) [hbase] Regions are still being
 doubly assigned
In-Reply-To: <6649469.1187985810705.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HADOOP-1780:
--------------------------

    Fix Version/s: 0.15.0
         Assignee: stack
           Status: Patch Available  (was: Open)

Builds local and passes all test.  Trying against Hudson.

> [hbase] Regions are still being doubly assigned
> -----------------------------------------------
>
>                 Key: HADOOP-1780
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1780
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>             Fix For: 0.15.0
>
>         Attachments: hadoop-1780.patch
>
>
> HADOOP-1747 fixed an obvious failure in assignment code where regions were being handed out to multiple hosts by the twos and threes but a bug remains.  Over 260 assignments in a recent upload to a cluster of 4 machines, two regions were assigned to two different hosts.  Here's log snippet from master showing region being assigned to two different hosts:
> {code}
> ...
> 2007-08-24 02:48:35,077 INFO org.apache.hadoop.hbase.HMaster: assigning region hbaserepository,kABjAiU049peySkC0-5iWk==,6867001475682921877 to server 208.76.44.140:60010
> ...
> 2007-08-24 02:48:36,299 INFO org.apache.hadoop.hbase.HMaster: assigning region hbaserepository,kABjAiU049peySkC0-5iWk==,6867001475682921877 to server 208.76.44.141:60010
> ...
> {code}

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