[jira] [Commented] (HBASE-8951) DNS not resolving should no longer show in logs as ERROR

["Masatake Iwasaki (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753576#comment-13753576 ] 

Masatake Iwasaki commented on HBASE-8951:
-----------------------------------------

The reason why TableInputFormatBase uses reverseDNS (HBASE-5259) seems to be for task locality.
Though I agree that WARN is more appropriate than ERROR, the description about DNS in HBase Book which is based on HBASE-3431 does not mean that the logic in TableInputFormatBase is not necessary.

                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira