[ https://issues.apache.org/jira/browse/HBASE-17677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880068#comment-15880068 ]
Hudson commented on HBASE-17677: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2555 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2555/]) HBASE-17677 ServerName parsing from directory name should be more robust (busbey: rev 040b2f186a08222fc0a0b3bd5c97ccef9cf45368) * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestWALMethods.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/AbstractFSWALProvider.java > 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, 1.4.0, 1.3.1, 1.2.5, 1.1.10 > > Attachments: HBASE-17677.1.patch > > > 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)