Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "UnknownHost" page has been changed by SteveLoughran: https://wiki.apache.org/hadoop/UnknownHost?action=diff&rev1=8&rev2=9 Comment: add reference to cloud infra 1. The hostname in the configuration files (such as {{{core-site.xml}}}) is confused with the hostname of another service. For example, you are using the hostname of the YARN Resource Manager in the {{{fs.defaultFS}}} configuration option to define the namenode. 1. A worker node thinks it has a given name which it reports to the NameNode and JobTracker, but that isn't the name that the network team gave it, so it isn't resolvable. 1. The calling machine is on a different subnet from the target machine, and short names are being used instead of fully qualified domain names (FQDNs). + 1. You are running in a cloud infrastructure and the destination machine is no longer there. It may have been deleted from the DNS records, or, due to some race condition, something is trying to talk to a host that hasn't been created yet. + Less likely causes: 1. The client's network card is playing up (network timeouts, etc), the network is overloaded, or even the switch is dropping DNS packets.
