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 73DEA200C1F for ; Sat, 18 Feb 2017 14:18:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6BECC160B66; Sat, 18 Feb 2017 13:18:57 +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 AFD5C160B63 for ; Sat, 18 Feb 2017 14:18:56 +0100 (CET) Received: (qmail 37836 invoked by uid 500); 18 Feb 2017 13:18:55 -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 37819 invoked by uid 99); 18 Feb 2017 13:18:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Feb 2017 13:18:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3A4731A0082 for ; Sat, 18 Feb 2017 13:18:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id bfBGoynelmI3 for ; Sat, 18 Feb 2017 13:18: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 D31C15F610 for ; Sat, 18 Feb 2017 13:18:46 +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 C696BE0146 for ; Sat, 18 Feb 2017 13:18:45 +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 D7A622411B for ; Sat, 18 Feb 2017 13:18:44 +0000 (UTC) Date: Sat, 18 Feb 2017 13:18:44 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17657) TestZKAsyncRegistry is flaky MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 18 Feb 2017 13:18:57 -0000 [ https://issues.apache.org/jira/browse/HBASE-17657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873155#comment-15873155 ] Duo Zhang commented on HBASE-17657: ----------------------------------- As we are going to test ZKAsyncRegistry here, we should not rely on the result of it when constructing the test? We should use other methods to detect if all the replicas for meta region is ready. > TestZKAsyncRegistry is flaky > ----------------------------- > > Key: HBASE-17657 > URL: https://issues.apache.org/jira/browse/HBASE-17657 > Project: HBase > Issue Type: Test > Reporter: Ted Yu > Assignee: Ted Yu > Attachments: 17657.v1.txt > > > TestZKAsyncRegistry showed up in failed tests several times. > On https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html , TestZKAsyncRegistry is reported flaky 33% of the time. > e.g. > https://builds.apache.org/job/PreCommit-HBASE-Build/5708/testReport/org.apache.hadoop.hbase.client/TestZKAsyncRegistry/test/ > Toward the end of test output: > {code} > 2017-02-14 20:23:20,779 WARN [main-EventThread] client.ZKAsyncRegistry(198): Meta region for replica 2 is in state PENDING_OPEN > 2017-02-14 20:23:20,800 INFO [98410feec74d:45445.activeMasterManager] hbase.MetaTableAccessor(1767): Updated table hbase:meta state to ENABLED in META > 2017-02-14 20:23:20,804 DEBUG [PostOpenDeployTasks:534574363] regionserver.HRegionServer(2034): Finished post open deploy task for hbase:meta,,1_0001.534574363 > 2017-02-14 20:23:20,811 DEBUG [RS_OPEN_META-98410feec74d:50745-0] handler.OpenRegionHandler(126): Opened hbase:meta,,1_0001.534574363 on 98410feec74d,50745,1487103793930 > {code} > Looks like some replica of the hbase:meta table might not have finished opening by the time the test asserted region location not being null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)