Closed elbrujohalcon closed 5 years ago
I've added support for passing a flag --id=<string with valid node name chars>
to all of the release commands which take --name
and --cookie
; you can use this to uniquely identify tasks for multiple concurrent connections.
The reason I didn't autogenerate IDs is because node names are atoms, and when connecting to a node those atoms end up in both atom tables, after enough time of your tasks running, a node could blow the atom table limit, so it is better to decide on names per-task, so that those names are re-used each time that task runs.
Cool. Thanks :)
Steps to reproduce
The steps to reproduce this bug are:
my_app
)._build/dev/rel/my_app/bin/my_app console_clean
).build/my_app/bin/my_app rpc "Process.sleep(10000)
).build/my_app/bin/my_app ping
).At this point, you should see your
ping
crashing with a message like …Description of issue
Associated code
I was able to track down the issue to
Mix.Releases.Runtime.Control.suffix_name/1,2
, where a hardcoded name is assigned to maintenance nodes.