hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3243) Disable Table closed region on wrong host
Date Mon, 29 Nov 2010 20:27:12 GMT

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

stack commented on HBASE-3243:
------------------------------

Did you intend to do this in your patch Jon?

{code}
@@ -1359,11 +1361,6 @@
     }
     synchronized (this.regions) {
       this.regions.remove(hri);
-    }
-    synchronized (this.regionPlans) {
-      this.regionPlans.remove(hri.getEncodedName());
-    }
-    synchronized (this.servers) {
       for (List<HRegionInfo> regions : this.servers.values()) {
         for (int i=0;i<regions.size();i++) {
           if (regions.get(i).equals(hri)) {
{code}

> Disable Table closed region on wrong host
> -----------------------------------------
>
>                 Key: HBASE-3243
>                 URL: https://issues.apache.org/jira/browse/HBASE-3243
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.90.0
>
>         Attachments: hbase-3243-logs.tar.bz2, HBASE-3243-v1.patch, hri.diff
>
>
> I ran some YCSB benchmarks which resulted in about 150 regions worth of data overnight.
Then I disabled the table, and the master for some reason closed one region on the wrong server.
The server ignored this, but the region remained open on a different server, which later flipped
out when it tried to flush due to hlog accumulation.

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


Mime
View raw message