[
https://issues.apache.org/jira/browse/HDFS-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655292#comment-15655292
]
Andres Perez edited comment on HDFS-8307 at 11/10/16 10:02 PM:
---------------------------------------------------------------
Hi [~anu],
Sorry for the wait I was setting up an HA cluster with a trunk build, and the
problem does not appear to be there. The rework and new logic must have solved
this in 2.8
was (Author: aaperezl):
Hi [~anu],
Sorry for the wait I was setting up an HA cluster with a trunk build, and the
problem does not appear to be there. The rework and new logic must have removed
this in 2.8
> Spurious DNS Queries from hdfs shell
> ------------------------------------
>
> Key: HDFS-8307
> URL: https://issues.apache.org/jira/browse/HDFS-8307
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.1
> Reporter: Anu Engineer
> Assignee: Andres Perez
> Priority: Trivial
> Labels: ha
> Fix For: 2.7.4
>
> Attachments: HDFS-8307-branch-2.7.patch, HDFS-8307.001.patch
>
>
> With HA configured the hdfs shell (org.apache.hadoop.fs.FsShell) seems to
> issue a DNS query for the cluster Name. if fs.defaultFS is set to
> hdfs://mycluster, then the shell seems to issue a DNS query for
> mycluster.FQDN or mycluster.
> since mycluster not a machine name DNS query always fails with
> "DNS 85 Standard query response 0x2aeb No such name"
> Repro Steps:
> # Setup a HA cluster
> # Log on to any node
> # Run wireshark monitoring port 53 - "sudo tshark 'port 53'"
> # Run "sudo -u hdfs hdfs dfs -ls /"
> # You should be able to see DNS queries to mycluster.FQDN in wireshark
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
