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 12C0A200D37 for ; Thu, 9 Nov 2017 19:48:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 112BD160C02; Thu, 9 Nov 2017 18:48:05 +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 570EB1609C8 for ; Thu, 9 Nov 2017 19:48:04 +0100 (CET) Received: (qmail 22947 invoked by uid 500); 9 Nov 2017 18:48:03 -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 22936 invoked by uid 99); 9 Nov 2017 18:48:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2017 18:48:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 91E2BD5BFF for ; Thu, 9 Nov 2017 18:48:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id jLudg404EOLx for ; Thu, 9 Nov 2017 18:48:01 +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 5F4E861027 for ; Thu, 9 Nov 2017 18:48: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 9A3CEE0D1F for ; Thu, 9 Nov 2017 18:48: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 55846240D2 for ; Thu, 9 Nov 2017 18:48:00 +0000 (UTC) Date: Thu, 9 Nov 2017 18:48:00 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-19220) Async tests time out talking to zk; 'clusterid came back null' MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Nov 2017 18:48:05 -0000 [ https://issues.apache.org/jira/browse/HBASE-19220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19220: -------------------------- Resolution: Fixed Release Note: Changed retries from 3 to 30 for zk initial connect for registry. Status: Resolved (was: Patch Available) Push to branch-2 and master. > Async tests time out talking to zk; 'clusterid came back null' > -------------------------------------------------------------- > > Key: HBASE-19220 > URL: https://issues.apache.org/jira/browse/HBASE-19220 > Project: HBase > Issue Type: Sub-task > Components: test > Reporter: stack > Assignee: stack > Fix For: 2.0.0-beta-1 > > Attachments: 19220.patch > > > I see this in test runs on a dedicated machine: > [ERROR] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 652.514 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestAsyncAdminBuilder > [ERROR] testRpcTimeout[0](org.apache.hadoop.hbase.client.TestAsyncAdminBuilder) Time elapsed: 213.618 s <<< ERROR! > java.util.concurrent.ExecutionException: java.io.IOException: clusterid came back null > at org.apache.hadoop.hbase.client.TestAsyncAdminBuilder.testRpcTimeout(TestAsyncAdminBuilder.java:105) > Caused by: java.io.IOException: clusterid came back null > [ERROR] org.apache.hadoop.hbase.client.TestAsyncTableScanMetrics Time elapsed: 0.007 s <<< ERROR! > java.util.concurrent.ExecutionException: java.io.IOException: clusterid came back null > at org.apache.hadoop.hbase.client.TestAsyncTableScanMetrics.setUp(TestAsyncTableScanMetrics.java:97) > Caused by: java.io.IOException: clusterid came back null > [ERROR] org.apache.hadoop.hbase.client.TestRawAsyncScanCursor Time elapsed: 0.005 s <<< ERROR! > java.util.concurrent.ExecutionException: java.io.IOException: clusterid came back null > at org.apache.hadoop.hbase.client.TestRawAsyncScanCursor.setUpBeforeClass(TestRawAsyncScanCursor.java:42) > Caused by: java.io.IOException: clusterid came back null > [ERROR] org.apache.hadoop.hbase.client.TestAsyncNamespaceAdminApi Time elapsed: 0.005 s <<< ERROR! > java.util.concurrent.ExecutionException: java.io.IOException: clusterid came back null > at org.apache.hadoop.hbase.client.TestAsyncNamespaceAdminApi.setUpBeforeClass(TestAsyncNamespaceAdminApi.java:66) > Caused by: java.io.IOException: clusterid came back null > If I up the retries, they go away. > At least on this machine, I notice that zk connections can take a while... see HBASE-19102 where we add a wait on the Connection to come up before progressing. > Suggest that I up the retries. No harm in trying more. It is currently set to 3 retries at a one second interval. -- This message was sent by Atlassian JIRA (v6.4.14#64029)