ERL-440: too many nodes with the same name

[OTP-Maintainer]

Original reporter: boboxiaodd
Affected version: OTP-20.0
Component: kernel
Migrated from: https://bugs.erlang.org/browse/ERL-440

---

i don't know how happen,so many node with the same name...

[OTP-Maintainer]

rickard said:

You are most likely inspecting the system with a tool that show one entry for each thread of each process instead of only one entry for each process. If so, the printout is expected. By default the Erlang VM process has lots of threads.

[OTP-Maintainer]

boboxiaodd said:

This should be the result: I used init:stop () to stop the node and, for some reason, the node failed to shut down, causing memory to continue to increase and eventually crash. In this process, the node is restarted without error reporting, and perhaps the node check cannot connect to the old node, which was previously judged to be created. I solved the problem by stopping nodes with halt (1).

[OTP-Maintainer]

rickard said:

When calling {{init:stop()}} the node wont terminate until all ports have flushed their data and closed. halt(1) will not wait for flushes. If you want an exit result of zero, you can use:
{code}
halt(0, [{flush,false}])
{code}

See [erlang:halt/2|http://erlang.org/doc/man/erlang.html#halt-2].