[erlang-bugs] table referred to by foreign key does not have node pool properly cleaned up when a node is removed from the schema

[Matthew Dempsky]

2008/5/10 Paul Mineiro <paul-trapexit@REDACTED>:
> if we had not been
> able to create a machine that had the same node name as the one removed,
> i'm not quite sure how we would have navigated around this in our
> production system, short of restore from backup.

For what it's worth, at least when using long node names, you can
assign whatever arbitrary name you want to a node.  E.g., there's
nothing stopping me from running "erl -name foo@REDACTED" or "erl
-name bar@REDACTED" on my laptop right now.  The only catch is that
this node needs to be the one to initiate all distribution
connections.