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 B0F3018A71 for ; Tue, 29 Sep 2015 07:49:04 +0000 (UTC) Received: (qmail 51604 invoked by uid 500); 29 Sep 2015 07:49:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51548 invoked by uid 500); 29 Sep 2015 07:49:04 -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 51531 invoked by uid 99); 29 Sep 2015 07:49:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2015 07:49:04 +0000 Date: Tue, 29 Sep 2015 07:49:04 +0000 (UTC) From: "Nick Dimiduk (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-13627) Terminating RS results in redundant CLOSE RPC 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-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13627: --------------------------------- Fix Version/s: (was: 1.1.3) 1.1.4 > Terminating RS results in redundant CLOSE RPC > --------------------------------------------- > > Key: HBASE-13627 > URL: https://issues.apache.org/jira/browse/HBASE-13627 > Project: HBase > Issue Type: Bug > Components: master > Affects Versions: 1.1.0 > Reporter: Nick Dimiduk > Priority: Minor > Labels: beginner, beginners > Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4 > > > Noticed while testing the 1.1.0RC0 bits. It seems we're issuing a redundant close RPC during shutdown. This results in a logging warning for each region. > {noformat} > 2015-05-06 00:07:19,214 INFO [RS:0;ndimiduk-apache-1-1-dist-6:56371] regionserver.HRegionServer: Received CLOSE for the region: 19cbe4fe2fe5335e7aace05e10e36ede, which we are already trying to CLOSE, but not completed yet > 2015-05-06 00:07:19,214 WARN [RS:0;ndimiduk-apache-1-1-dist-6:56371] regionserver.HRegionServer: Failed to close cluster_test,66666666,1430869443384.19cbe4fe2fe5335e7aace05e10e36ede. - ignoring and continuing > org.apache.hadoop.hbase.regionserver.RegionAlreadyInTransitionException: The region 19cbe4fe2fe5335e7aace05e10e36ede was already closing. New CLOSE request is ignored. > at org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegion(HRegionServer.java:2769) > at org.apache.hadoop.hbase.regionserver.HRegionServer.closeRegionIgnoreErrors(HRegionServer.java:2695) > at org.apache.hadoop.hbase.regionserver.HRegionServer.closeUserRegions(HRegionServer.java:2327) > at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:937) > at java.lang.Thread.run(Thread.java:745) > {noformat} > 1. launch a standalone cluster from tgz (./bin/start-hbase.sh) > 2. load some data (ie, run bin/hbase ltt) > 3. terminate cluster (./bin/stop-hbase.sh) -- This message was sent by Atlassian JIRA (v6.3.4#6332)