[ 
https://issues.apache.org/jira/browse/HBASE-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229801#comment-13229801
 ] 

Jonathan Hsieh commented on HBASE-5563:
---------------------------------------

A bunch of the failures have been fixed with this addition, but there are a 
still a few remaining to hunt down.

{code}
diff --git a/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
index 479861d..cad4314 100644
--- a/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
+++ b/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
@@ -2705,8 +2705,10 @@ public class AssignmentManager extends ZooKeeperListener 
    */
   public List<HRegionInfo> getRegionsOfTable(byte[] tableName) {
     List<HRegionInfo> tableRegions = new ArrayList<HRegionInfo>();
+    // boundary needs to have table's name but regionID 0 so that it is sorted 
+    // before all table's regions.
     HRegionInfo boundary =
-      new HRegionInfo(tableName, null, null);
+      new HRegionInfo(tableName, null, null, false, 0L);
     synchronized (this.regions) {
       for (HRegionInfo regionInfo: this.regions.tailMap(boundary).keySet()) {
         if(Bytes.equals(regionInfo.getTableName(), tableName)) {
{code}
                
> HRegionInfo#compareTo add the comparison of regionId
> ----------------------------------------------------
>
>                 Key: HBASE-5563
>                 URL: https://issues.apache.org/jira/browse/HBASE-5563
>             Project: HBase
>          Issue Type: Bug
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-5563.patch, HBASE-5563v2.patch, HBASE-5563v2.patch
>
>
> In the one region multi assigned case,  we could find that two regions have 
> the same table name, same startKey, same endKey, and different regionId, so 
> these two regions are same in TreeMap but different in HashMap.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to