Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 598DF10D35 for ; Fri, 24 Oct 2014 09:08:34 +0000 (UTC) Received: (qmail 56792 invoked by uid 500); 24 Oct 2014 09:08:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56741 invoked by uid 500); 24 Oct 2014 09:08:34 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 56729 invoked by uid 99); 24 Oct 2014 09:08:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Oct 2014 09:08:33 +0000 Date: Fri, 24 Oct 2014 09:08:33 +0000 (UTC) From: "Liu Shaohui (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-12336) RegionServer failed to shutdown for NodeFailoverWorker thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-12336: -------------------------------- Attachment: stack jstack of the regionserver. > RegionServer failed to shutdown for NodeFailoverWorker thread > ------------------------------------------------------------- > > Key: HBASE-12336 > URL: https://issues.apache.org/jira/browse/HBASE-12336 > Project: HBase > Issue Type: Bug > Affects Versions: 0.94.11 > Reporter: Liu Shaohui > Assignee: Liu Shaohui > Priority: Minor > Attachments: stack > > > After enabling hbase.zookeeper.useMulti in hbase cluster, we found that regionserver failed to shutdown. Other threads have exited except a NodeFailoverWorker thread. > {code} > "ReplicationExecutor-0" prio=10 tid=0x00007f0d40195ad0 nid=0x73a in Object.wait() [0x00007f0dc8fe6000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:485) > at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1309) > - locked <0x00000005a16df080> (a org.apache.zookeeper.ClientCnxn$Packet) > at org.apache.zookeeper.ZooKeeper.multiInternal(ZooKeeper.java:930) > at org.apache.zookeeper.ZooKeeper.multi(ZooKeeper.java:912) > at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.multi(RecoverableZooKeeper.java:531) > at org.apache.hadoop.hbase.zookeeper.ZKUtil.multiOrSequential(ZKUtil.java:1518) > at org.apache.hadoop.hbase.replication.ReplicationZookeeper.copyQueuesFromRSUsingMulti(ReplicationZookeeper.java:804) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager$NodeFailoverWorker.run(ReplicationSourceManager.java:612) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > {code} > It's sure that the shutdown method of the executor is called in ReplicationSourceManager#join. > > I am looking for the root cause and suggestions are welcomed. Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)