Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5401FDB1F for ; Wed, 13 Feb 2013 10:58:16 +0000 (UTC) Received: (qmail 92276 invoked by uid 500); 13 Feb 2013 10:58:15 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 91773 invoked by uid 500); 13 Feb 2013 10:58:14 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 91699 invoked by uid 99); 13 Feb 2013 10:58:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Feb 2013 10:58:12 +0000 Date: Wed, 13 Feb 2013 10:58:12 +0000 (UTC) From: "Damien Hardy (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-7838) HBase regionserver never stoping when runing `hbase-daemon.sh stop regionserver` MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Damien Hardy created HBASE-7838: ----------------------------------- Summary: HBase regionserver never stoping when runing `hbase-daemon.sh stop regionserver` Key: HBASE-7838 URL: https://issues.apache.org/jira/browse/HBASE-7838 Project: HBase Issue Type: Bug Components: regionserver, scripts, shell Affects Versions: 0.94.4, 0.92.1, 0.96.0 Environment: Using CDH4.1.2 Reporter: Damien Hardy Currently running full stack (Hadoop + Hbase + zookeeper) on a VM I want to reboot, every services stopped but HBase regionserver. For 2 days now, it's aligning dots on the console ... I propose a timeout (default 600 overidable by $HBASE_STOP_TIMEOUT) to force kill -9 on the process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira