Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E769D200C53 for ; Tue, 28 Mar 2017 03:17:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E5DC4160B99; Tue, 28 Mar 2017 01:17:50 +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 3A97D160B85 for ; Tue, 28 Mar 2017 03:17:50 +0200 (CEST) Received: (qmail 75502 invoked by uid 500); 28 Mar 2017 01:17:49 -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 75491 invoked by uid 99); 28 Mar 2017 01:17:49 -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; Tue, 28 Mar 2017 01:17:49 +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 BD0DAC0096 for ; Tue, 28 Mar 2017 01:17:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id j6yclXP4QXZp for ; Tue, 28 Mar 2017 01:17:47 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4D94A5F341 for ; Tue, 28 Mar 2017 01:17:47 +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 D0061E02EF for ; Tue, 28 Mar 2017 01:17:42 +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 F1E4224062 for ; Tue, 28 Mar 2017 01:17:41 +0000 (UTC) Date: Tue, 28 Mar 2017 01:17:41 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17287) Master becomes a zombie if filesystem object closes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 01:17:51 -0000 [ https://issues.apache.org/jira/browse/HBASE-17287?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D159= 44353#comment-15944353 ]=20 Ted Yu commented on HBASE-17287: -------------------------------- bq. Why is it inside TestCreateTableProcedure I created TestSafemodeBringsDownMaster for the new test. bq. Why are we aborting the regionserver? The region server, hosting meta, has unflushed edits. This simulates the sc= enario Clay reported. > Master becomes a zombie if filesystem object closes > --------------------------------------------------- > > Key: HBASE-17287 > URL: https://issues.apache.org/jira/browse/HBASE-17287 > Project: HBase > Issue Type: Bug > Components: master > Reporter: Clay B. > Assignee: Ted Yu > Fix For: 1.4.0, 2.0 > > Attachments: 17287.branch-1.1.v4.txt, 17287.branch-1.v3.txt, 1728= 7.branch-1.v4.txt, 17287.master.v2.txt, 17287.master.v3.txt, 17287.master.v= 4.txt, 17287.v2.txt > > > We have seen an issue whereby if the HDFS is unstable and the HBase maste= r's HDFS client is unable to stabilize before {{dfs.client.failover.max.att= empts}} then the master's filesystem object closes. This seems to result in= an HBase master which will continue to run (process and znode exists) but = no meaningful work can be done (e.g. assigning meta).What we saw in our HBa= se master logs was:{code}2016-12-01 19:19:08,192 ERROR org.apache.hadoop.hb= ase.master.handler.MetaServerShutdownHandler: Caught M_META_SERVER_SHUTDOWN= , count=3D1java.io.IOException: failed log splitting for cluster-r5n12.bloo= mberg.com,60200,1480632863218, will retryat org.apache.hadoop.hbase.master.= handler.MetaServerShutdownHandler.process(MetaServerShutdownHandler.java:84= )at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:129= )at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja= va:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe= cutor.java:617)at java.lang.Thread.run(Thread.java:745)Caused by: java.io.I= OException: Filesystem closed{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)