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 93116200C23 for ; Wed, 22 Feb 2017 17:42:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 91AFB160B62; Wed, 22 Feb 2017 16:42:53 +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 D96B9160B49 for ; Wed, 22 Feb 2017 17:42:52 +0100 (CET) Received: (qmail 48119 invoked by uid 500); 22 Feb 2017 16:42:52 -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 48108 invoked by uid 99); 22 Feb 2017 16:42:52 -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, 22 Feb 2017 16:42:52 +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 973C2189A8F for ; Wed, 22 Feb 2017 16:42:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id VvwUCtbs6nzJ for ; Wed, 22 Feb 2017 16:42:48 +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 35A545FACC for ; Wed, 22 Feb 2017 16:42:48 +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 590F5E00D6 for ; Wed, 22 Feb 2017 16:42:44 +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 1684A2411D for ; Wed, 22 Feb 2017 16:42:44 +0000 (UTC) Date: Wed, 22 Feb 2017 16:42:44 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-17677) ServerName parsing from directory name should be more robust to errors from guava's HostAndPort MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 22 Feb 2017 16:42:53 -0000 Sean Busbey created HBASE-17677: ----------------------------------- Summary: ServerName parsing from directory name should be more robust to errors from guava's HostAndPort Key: HBASE-17677 URL: https://issues.apache.org/jira/browse/HBASE-17677 Project: HBase Issue Type: Bug Components: wal Affects Versions: 2.0.0 Reporter: Sean Busbey Assignee: Sean Busbey Fix For: 2.0.0 our internal Address facade over HostAndPort directly passes on any failures from the underlying Guava implementation. Right now when we parse a ServerName from a WAL directory we properly handle if guava gives us an IllegalArgumentException but we do not handle if it gives us a IllegalStateException. e.g. it uses the former for "I couldn't parse anything out of this string" and the latter for "I parsed a host name but didn't see a port". -- This message was sent by Atlassian JIRA (v6.3.15#6346)