EPMD is the daemon of the port mapping between Erlang cluster nodes, which is responsible for maintaining the node connection in the cluster , providing the node name to IP address and Port resolution service.
EPMD Custom Port numbersEPMD Port ConfigurationBy default, EPMD is bound to Port 4369. However, if the port is fixed, it is vulnerable to attack, which may cause the authentication of the new node to fail to start or to join the cluster.
If you want to start EPMD with debug mode, use epmd-d-port
In addition, the EPMD is usually associated with the automatic start-up of the Erlang node and does not require manual processing, so it is also possible to adjust the Erl startup parameters to automatically tune the EPMD port.
Erl-name [email protected] -EPMD "Epmd-port 5000-daemon"
|
node Start configurationwhen the EPMD port is changed, theErlang node needs to explicitly specify the EPMD port information. under Windwos, Erlang starts as follows:
C:\>set erl_epmd_port=5000
C:\>erl-name [email protected]
|
Note that the above command port number (here is the) can not leave a space before and after. under Linux, theErlang boot method is as follows:
| erl_epmd_port=5000 erl-name [email protected] |
EPMD Related Issuesrestrict the nodes of the specified IP to join the cluster
| Epmd-port 5000-address 127.0.0.1-daemon |
this way, if the node name is not [email protected], it will not start or join the cluster.
How to kill the EPMD processThe EPMD is independent of the Erlang node and continues to exist after all nodes are closed, and sometimes the EPMD process may need to be killed.
Reference: http://blog.csdn.net/mycwq/article/details/46630743
Erlang EPMD Custom Port numbers
