You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Marc Reichman (JIRA)" <ji...@apache.org> on 2013/01/17 23:32:12 UTC

[jira] [Created] (HBASE-7618) Reverse DNS in TableInputFormat still leaves trailing period

Marc Reichman created HBASE-7618:
------------------------------------

             Summary: Reverse DNS in TableInputFormat still leaves trailing period
                 Key: HBASE-7618
                 URL: https://issues.apache.org/jira/browse/HBASE-7618
             Project: HBase
          Issue Type: Bug
          Components: mapreduce
    Affects Versions: 0.94.2
         Environment: Linux CentOS 6.3 x64, Oracle JDK 6u27 x64
            Reporter: Marc Reichman


There have been several tickets dealing with reverse DNS inconsistencies causing issues in HBase. I have found that using the TableMapper and TableInputFormat with HBase leads to a situation where there is no data locality in situations where the task tracker DNS name and input split location provided by the input format differ by a trailing period.

In this case I have 0% data-local and 100% rack-local map tasks which take on this format:

task host: /default-rack/hostname.ext
input split: /default-rack/hostname.ext.

It seems to be a crapshoot on whether the task will land on the proper host. The reverse DNS seems to be done differently for this class compared to the others already fixed; It uses the hadoop core DNS util class.

--
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