[erlang-bugs] Weird documentation of distributed applications

[Loïc Hoguin]

Hello,

I got pointed at a weirdness in the documentation by Eric Pailleau. This 
chapter:
 
http://www.erlang.org/doc/design_principles/distributed_applications.html#id74957

says:

"The system configuration files for cp2@REDACTED and cp3@REDACTED are identical, 
except for the list of mandatory nodes which should be [cp1@REDACTED, 
cp3@REDACTED] for cp2@REDACTED and [cp1@REDACTED, cp2@REDACTED] for cp3@REDACTED"

First, that's incredibly clumsy. Having a different configuration file 
per node like this is just impractical if you're going to have 50 of them.

But looking at the code it appears you can actually put [cp1@REDACTED, 
cp2@REDACTED, cp3@REDACTED] everywhere, because all this does is to ping 
everything and make sure they're up before continuing. A ping to 
yourself *does* work so that makes the whole sentence pointless.

What to do?

-- 
Loïc Hoguin
Erlang Cowboy
Nine Nines
http://ninenines.eu