You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 17:26:00 UTC
[jira] [Resolved] (HBASE-8951) DNS not resolving should no longer show in logs as ERROR
[ https://issues.apache.org/jira/browse/HBASE-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-8951.
----------------------------------------
Resolution: Invalid
> DNS not resolving should no longer show in logs as ERROR
> --------------------------------------------------------
>
> Key: HBASE-8951
> URL: https://issues.apache.org/jira/browse/HBASE-8951
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.5
> Reporter: Ron Echeverri
> Priority: Minor
>
> Current error message from an hbase-0.94.5 installation:
> {{ERROR mapreduce.TableInputFormatBase: Cannot resolve the host name for /192.168.254.178 because of javax.naming.CommunicationException: DNS error [Root exception is java.net.PortUnreachableException: ICMP Port Unreachable]; remaining name '178.254.168.192.in-addr.arpa'}}
> According to the Book, "Both forward and reverse DNS resolving must work in versions of HBase previous to 0.92.0." Given that since 0.92.0, forward/reverse DNS is not required, this should be a WARN and not an ERROR.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)