Database Reference
In-Depth Information
listen on. A port number of 0 instructs the server to start on a free port, but this is gener-
ally discouraged because it is incompatible with setting cluster-wide firewall policies.
In general, the properties for setting a server's RPC and HTTP addresses serve double
duty: they determine the network interface that the server will bind to, and they are used
by clients or other machines in the cluster to connect to the server. For example, node
managers use the
yarn.resourcemanager.resource-tracker.address
property to find the address of their resource manager.
It is often desirable for servers to bind to multiple network interfaces, but setting the net-
work address to
0.0.0.0
, which works for the server, breaks the second case, since the
address is not resolvable by clients or other machines in the cluster. One solution is to
have separate configurations for clients and servers, but a better way is to set the bind host
for the server. By setting
yarn.resourcemanager.hostname
to the (externally
resolvable) hostname or IP address and
yarn.resourcemanager.bind-host
to
0.0.0.0
, you ensure that the resource manager will bind to all addresses on the ma-
chine, while at the same time providing a resolvable address for node managers and cli-
ents.
In addition to an RPC server, datanodes run a TCP/IP server for block transfers. The serv-
er address and port are set by the
dfs.datanode.address
property , which has a de-
fault value of
0.0.0.0:50010
.
