Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <32974406.237251290448454700.JavaMail.jira@thor>
Date: Mon, 22 Nov 2010 12:54:14 -0500 (EST)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-3243) Disable Table closed region on wrong
 host
In-Reply-To: <32229030.137191289969893372.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HBASE-3243:
------------------------------------

Thanks for looking at this, Jon. I can run some tests with my "crazy config" which generates lots and lots of regions, and see if it happens again. Any good log messages you can suggest adding for this test?

> 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
>
>
> 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.