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 5D86C17BCA for ; Sat, 11 Apr 2015 01:01:15 +0000 (UTC) Received: (qmail 50855 invoked by uid 500); 11 Apr 2015 01:01:13 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 50734 invoked by uid 500); 11 Apr 2015 01:01:13 -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 50529 invoked by uid 99); 11 Apr 2015 01:01:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Apr 2015 01:01:13 +0000 Date: Sat, 11 Apr 2015 01:01:12 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-5023) A thread named LeaseChecker remains after the shutdown of a cluster 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-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-5023. ----------------------------------- Resolution: Not A Problem > A thread named LeaseChecker remains after the shutdown of a cluster > ------------------------------------------------------------------- > > Key: HBASE-5023 > URL: https://issues.apache.org/jira/browse/HBASE-5023 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 0.94.0 > Environment: all > Reporter: Nicolas Liochon > Priority: Minor > > If the minicluster is started/stopped multiple time, there is a new LeaseChecker each time. This thread is not created by HBase but by hdfs. > This is likely to be HDFS-1840, solved in 0.23 -- This message was sent by Atlassian JIRA (v6.3.4#6332)