Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <27337654.94651295567385674.JavaMail.jira@thor>
Date: Thu, 20 Jan 2011 18:49:45 -0500 (EST)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Resolved: (HBASE-3449) Server shutdown handlers deadlocked
 waiting for META
In-Reply-To: <23982690.22781295300144716.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-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-3449.
--------------------------

    Resolution: Fixed

I committed the below workaround to branch and trunk and opened HBASE-3458 to fix it so issue cannot ever happen.

{code}
Index: src/main/java/org/apache/hadoop/hbase/master/HMaster.java
===================================================================
--- src/main/java/org/apache/hadoop/hbase/master/HMaster.java   (revision 1061564)
+++ src/main/java/org/apache/hadoop/hbase/master/HMaster.java   (working copy)
@@ -518,7 +518,7 @@
       this.executorService.startExecutorService(ExecutorType.MASTER_SERVER_OPERATIONS,
         conf.getInt("hbase.master.executor.serverops.threads", 3));
       this.executorService.startExecutorService(ExecutorType.MASTER_META_SERVER_OPERATIONS,
-        conf.getInt("hbase.master.executor.serverops.threads", 2));
+        conf.getInt("hbase.master.executor.serverops.threads", 5));
       // We depend on there being only one instance of this executor running
       // at a time.  To do concurrency, would need fencing of enable/disable of
       // tables.
{code}

> Server shutdown handlers deadlocked waiting for META
> ----------------------------------------------------
>
>                 Key: HBASE-3449
>                 URL: https://issues.apache.org/jira/browse/HBASE-3449
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.90.1
>
>
> I have a situation where both of my MASTER_META_SERVER_OPERATIONS handlers are handling server shutdowns, and both of them are waiting on ROOT, which isn't coming up. Unclear exactly how this happened, but I triggered it by doing a rolling restart.

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