From dev-return-50174-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Thu Mar 15 08:44:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 97C4E180649 for ; Thu, 15 Mar 2018 08:44:04 +0100 (CET) Received: (qmail 59028 invoked by uid 500); 15 Mar 2018 07:44:03 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 59015 invoked by uid 99); 15 Mar 2018 07:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2018 07:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C8091C0366 for ; Thu, 15 Mar 2018 07:44:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Sdd6Q2I7AHXX for ; Thu, 15 Mar 2018 07:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 4AD5D5F238 for ; Thu, 15 Mar 2018 07:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 98701E0446 for ; Thu, 15 Mar 2018 07:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 22EFA21495 for ; Thu, 15 Mar 2018 07:44:00 +0000 (UTC) Date: Thu, 15 Mar 2018 07:44:00 +0000 (UTC) From: "sanket patel (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-3977) Region is not closed when moving region or balancing while writing to table with local index MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-3977?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 400044#comment-16400044 ]=20 sanket patel commented on PHOENIX-3977: --------------------------------------- I hit the similar issue recently with 4.10. I find regions in PENDING_CLOSE= state and same=C2=A0regions would show up under `/hbase-unsecure/regions-i= n-transition`=C2=A0 Znode. Also on HMaster UI, under Procedures tab, there = are pending tasks for DisableTable (probably because region is stuck) As a solution I remove the znode and restart hmaster. And then under same t= ables I see those regions as offline region. Later I drop table. Currently I am not able to reproduce the issue. I will post more symptoms a= nd things I notice if I happen to encounter it again. > Region is not closed when moving region or balancing while writing to tab= le with local index > -------------------------------------------------------------------------= ------------------- > > Key: PHOENIX-3977 > URL: https://issues.apache.org/jira/browse/PHOENIX-3977 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.10.0 > Reporter: JeongMin Ju > Priority: Major > Attachments: screenshot-1.png > > > Region is not closed when moving region or balancing while writing to tab= le with local index. > If the regionserver is forcibly killed and restart and then balancing is = performed during write operation perform using YCSB. The region is not move= d properly, so it becomes jammed. > This is also true when moving a specific region. > {panel:title=3DRegionServer1} > 2017-06-26 17:18:49,096 INFO org.apache.phoenix.hbase.index.util.IndexMan= agementUtil: Rethrowing org.apache.hadoop.hbase.DoNotRetryIOException: ERRO= R 2008 (INT10): ERROR 2008 (INT10): Unable to find cached index metadata. = key=3D-4998016164816556219 region=3DPHOENIX_TABLE,&,1498464285648.df3f3da32= 306361ce5e38e5193f5e5d6.host=3Djuke-cdh-36f531b4.s2.krane.9rum.cc,60020,149= 8464965204 Index update failed > 2017-06-26 17:18:49,531 INFO org.apache.phoenix.hbase.index.util.IndexMan= agementUtil: Rethrowing org.apache.hadoop.hbase.DoNotRetryIOException: ERRO= R 2008 (INT10): ERROR 2008 (INT10): Unable to find cached index metadata. = key=3D6036765365681157624 region=3DPHOENIX_TABLE,&,1498464285648.df3f3da323= 06361ce5e38e5193f5e5d6.host=3Djuke-cdh-36f531b4.s2.krane.9rum.cc,60020,1498= 464965204 Index update failed > 2017-06-26 17:18:49,536 INFO org.apache.phoenix.hbase.index.util.IndexMan= agementUtil: Rethrowing org.apache.hadoop.hbase.DoNotRetryIOException: ERRO= R 2008 (INT10): ERROR 2008 (INT10): Unable to find cached index metadata. = key=3D-428088766346522675 region=3DPHOENIX_TABLE,&,1498464285648.df3f3da323= 06361ce5e38e5193f5e5d6.host=3Djuke-cdh-36f531b4.s2.krane.9rum.cc,60020,1498= 464965204 Index update failed > {panel} > At other regionserver > {panel:title=3DRegionServer2} > 2017-06-26 17:19:49,755 INFO org.apache.hadoop.hbase.client.AsyncProcess:= #1476, waiting for 62 actions to finish on table: PHOENIX_TABLE > 2017-06-26 17:19:49,755 INFO org.apache.hadoop.hbase.client.AsyncProcess:= #1476, waiting for 27 actions to finish on table: PHOENIX_TABLE > 2017-06-26 17:19:49,755 INFO org.apache.hadoop.hbase.client.AsyncProcess:= #1476, waiting for 52 actions to finish on table: PHOENIX_TABLE > {panel} > phoenix.coprocessor.maxServerCacheTimeToLiveMs & phoenix.coprocessor.maxM= etaDataCacheSize was not effected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)