From issues-return-330625-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Tue Jan 23 18:41:09 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id A8A7C180621 for ; Tue, 23 Jan 2018 18:41:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 985AE160C24; Tue, 23 Jan 2018 17:41:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B8C29160C3A for ; Tue, 23 Jan 2018 18:41:08 +0100 (CET) Received: (qmail 3465 invoked by uid 500); 23 Jan 2018 17:41:07 -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 3454 invoked by uid 99); 23 Jan 2018 17:41:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2018 17:41:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3CDE8180807 for ; Tue, 23 Jan 2018 17:41:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.711 X-Spam-Level: X-Spam-Status: No, score=-108.711 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_LOW=-0.7, 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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ska2I8ccvQjX for ; Tue, 23 Jan 2018 17:41:06 +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 B1E1B5F1F3 for ; Tue, 23 Jan 2018 17:41:05 +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 ECD9CE09A5 for ; Tue, 23 Jan 2018 17:41:03 +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 DED4C25C61 for ; Tue, 23 Jan 2018 17:41:01 +0000 (UTC) Date: Tue, 23 Jan 2018 17:41:01 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-19710) hbase:namespace table was stuck in transition 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-19710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336129#comment-16336129 ] stack commented on HBASE-19710: ------------------------------- Make sure it an actual issue that destination is empty. It used to be a violation but throughout we made it so location could be null until assign last moment where it will pick up a location. > hbase:namespace table was stuck in transition > --------------------------------------------- > > Key: HBASE-19710 > URL: https://issues.apache.org/jira/browse/HBASE-19710 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Priority: Critical > Attachments: master-005-log.tar.gz, master-006.tar.gz, rs-009.log.tar.gz > > > ITBLL with chaos monkey failed due to namespace table getting stuck in transition. > From hbase-hbase-master-ctr-e137-1514896590304-3629-01-000006.hwx.site.log , we can see that master closed namespace table on 000009: > {code} > 2018-01-04 17:24:35,067 DEBUG [main-EventThread] zookeeper.ZKWatcher: master:20000-0x160c222710c0028, quorum=ctr-e137-1514896590304-3629-01-000011.hwx.site:2181,ctr-e137- 1514896590304-3629-01-000014.hwx.site:2181,ctr-e137-1514896590304-3629-01-000009.hwx.site:2181,ctr-e137-1514896590304-3629-01-000006.hwx.site:2181,ctr-e137-1514896590304-3629- 01-000003.hwx.site:2181,ctr-e137-1514896590304-3629-01-000007.hwx.site:2181,ctr-e137-1514896590304-3629-01-000013.hwx.site:2181,ctr-e137-1514896590304-3629-01-000002.hwx.site: 2181,ctr-e137-1514896590304-3629-01-000012.hwx.site:2181,ctr-e137-1514896590304-3629-01-000008.hwx.site:2181,ctr-e137-1514896590304-3629-01-000010.hwx.site:2181, baseZNode=/ hbase-unsecure Received ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected, path=/hbase-unsecure/rs > 2018-01-04 17:24:35,067 INFO [ProcExecWrkr-5] assignment.RegionStateStore: pid=643 updating hbase:meta row=hbase:namespace,,1515085217343.a95ed2d7434a43390fbec73abeeb9fd9., regionState=CLOSING, regionLocation=ctr-e137-1514896590304-3629-01-000009.hwx.site,16020,1515086643872 > ... > 2018-01-04 17:24:35,246 INFO [ProcExecWrkr-12] procedure.MasterProcedureScheduler: pid=647, ppid=642, state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure table=hbase: namespace, region=a95ed2d7434a43390fbec73abeeb9fd9 hbase:namespace hbase:namespace,,1515085217343.a95ed2d7434a43390fbec73abeeb9fd9. > 2018-01-04 17:25:17,041 DEBUG [ctr-e137-1514896590304-3629-01-000006:20000.masterManager] procedure2.ProcedureExecutor: Loading pid=641, state=WAITING:MOVE_REGION_ASSIGN; MoveRegionProcedure hri=hbase:namespace,,1515085217343.a95ed2d7434a43390fbec73abeeb9fd9., source=ctr-e137-1514896590304-3629-01-000009.hwx.site,16020,1515086643872, destination= > {code} > For the move operation, from ctr-e137-1514896590304-3629-01-000009.hwx.site log: > {code} > 2018-01-04 17:24:34,855 DEBUG [RS_CLOSE_REGION-ctr-e137-1514896590304-3629-01-000009:16020-0] coprocessor.CoprocessorHost: Stop coprocessor org.apache.hadoop.hbase.security. access.SecureBulkLoadEndpoint > 2018-01-04 17:24:34,855 INFO [RS_CLOSE_REGION-ctr-e137-1514896590304-3629-01-000009:16020-0] regionserver.HRegion: Closed hbase:namespace,,1515085217343. a95ed2d7434a43390fbec73abeeb9fd9. > 2018-01-04 17:24:34,856 DEBUG [RS_CLOSE_REGION-ctr-e137-1514896590304-3629-01-000009:16020-0] handler.CloseRegionHandler: Closed hbase:namespace,,1515085217343. a95ed2d7434a43390fbec73abeeb9fd9. > ... > 2018-01-04 17:25:47,607 DEBUG [RpcServer.priority.FPBQ.Fifo.handler=18,queue=0,port=16020] ipc.RpcServer: callId: 16 service: ClientService methodName: Get size: 103 connection: 172.27.13.80:36738 deadline: 1515086837568 > org.apache.hadoop.hbase.NotServingRegionException: hbase:namespace,,1515085217343.a95ed2d7434a43390fbec73abeeb9fd9. is not online on ctr-e137-1514896590304-3629-01-000009.hwx. site,16020,1515086719163 > at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:3312) > at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3289) > at org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:1354) > at org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:2360) > at org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:41544) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:403) > {code} > We can see that the region server was not serving the region. > After that, the masters kept thinking namespace table was on 0009, leading to prolonged downtime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)