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 7DC94200CA7 for ; Wed, 14 Jun 2017 22:03:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7BF10160BDB; Wed, 14 Jun 2017 20:03:04 +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 C3E60160BD6 for ; Wed, 14 Jun 2017 22:03:03 +0200 (CEST) Received: (qmail 65479 invoked by uid 500); 14 Jun 2017 20:03:02 -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 65468 invoked by uid 99); 14 Jun 2017 20:03:02 -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; Wed, 14 Jun 2017 20:03:02 +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 774A81806F7 for ; Wed, 14 Jun 2017 20:03:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 1Xh1D47ITu6A for ; Wed, 14 Jun 2017 20:03: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 109F35F6D3 for ; Wed, 14 Jun 2017 20:03: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 57296E070E for ; Wed, 14 Jun 2017 20:03: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 0949721D8F for ; Wed, 14 Jun 2017 20:03:00 +0000 (UTC) Date: Wed, 14 Jun 2017 20:03:00 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18178) [C++] Retrying meta location lookup and zookeeper connection MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 14 Jun 2017 20:03:04 -0000 [ https://issues.apache.org/jira/browse/HBASE-18178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049598#comment-16049598 ] Enis Soztutar commented on HBASE-18178: --------------------------------------- bq. Is the above going to be done in next patch or new JIRA ? We cannot do this in this jira. Will be follow up jira. bq. Why is the retry number increased ? Because retry number is 35 in the Java side. It should not have been 31. bq. Change the log level. (There're other LOG(INFO)'s in the patch) Log level is correct. It is intentionally INFO. bq. Is the return statement effective ? No it is not. However, we need it because of the static assertion for the folly::Future template. > [C++] Retrying meta location lookup and zookeeper connection > ------------------------------------------------------------- > > Key: HBASE-18178 > URL: https://issues.apache.org/jira/browse/HBASE-18178 > Project: HBase > Issue Type: Sub-task > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Attachments: hbase-18178-v1.patch > > > Currently location-cache can only do a single lookup to meta. If meta location changes or we have zookeeper connection problems, we never retry. -- This message was sent by Atlassian JIRA (v6.4.14#64029)