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 9A9AD102A5 for ; Thu, 27 Feb 2014 00:02:02 +0000 (UTC) Received: (qmail 79516 invoked by uid 500); 27 Feb 2014 00:01:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 79391 invoked by uid 500); 27 Feb 2014 00:01:26 -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 79351 invoked by uid 99); 27 Feb 2014 00:01:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Feb 2014 00:01:22 +0000 Date: Thu, 27 Feb 2014 00:01:22 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10614) Master could not be stopped 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-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913772#comment-13913772 ] Hudson commented on HBASE-10614: -------------------------------- FAILURE: Integrated in HBase-0.98 #187 (See [https://builds.apache.org/job/HBase-0.98/187/]) HBASE-10614 Master could not be stopped (Jingcheng Du) (stack: rev 1571916) * /hbase/branches/0.98/hbase-client/src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java * /hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java > Master could not be stopped > --------------------------- > > Key: HBASE-10614 > URL: https://issues.apache.org/jira/browse/HBASE-10614 > Project: HBase > Issue Type: Bug > Components: master > Affects Versions: 0.94.16, 0.99.0 > Reporter: Jingcheng Du > Assignee: Jingcheng Du > Fix For: 0.96.2, 0.98.1, 0.99.0, 0.94.18 > > Attachments: HBASE-10614-0.94.patch, HBASE-10614.patch > > > It's an issue when to run "bin/hbase master stop" to shutdown the cluster. > This could be reproduced by the following steps. Particularly for the trunk code, we need to configure the hbase.assignment.maximum.attempts as 1. > 1. Start one master and several region servers. > 2. Stop all the region servers. > 3. After a while, run "bin/hbase master stop" to shutdown the cluster. > As a result, the master could not be stopped within a short time, but will be stopped after several hours. And after it's stopped, i find the error logs. > 1. For the trunk: > A. lots of the logs which are "java.io.IOException: Failed to find location, tableName=hbase:meta, row=, reload=true" > B..And at last, there's one exception before the master is stopped, "ServerShutdownHandler: Received exception accessing hbase:meta during server shutdown of server-XXX, retrying hbase:meta read > java.io.InterruptedIOException: Interrupted after 0 tries on 350." > 2. For the branch 0.94: > A. lots of the logs which are "Looked up root region location, connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@44285d14; serverName=". > B. And at last, there's one exception before the master is stopped, "ServerShutdownHandler: Received exception accessing META during server shutdown of server-XXX, retrying META read > org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find region for after 140 tries." > We could see the master are stopped after lots of reties which are not necessary when the cluster is shutdown. -- This message was sent by Atlassian JIRA (v6.1.5#6160)