Erlang application will affect Erlang kernel net tick time operation ?.
If the Erlang application is loaded with too many print statements
i.e io:format, will it affect the Erlang kernel net tick time operation?.
and also I want to know, in what situation Erlang
"node_down_reason" as "connection_closed" will come.
Here I am running two Erlang nodes in visible mode
Example : a@HostIP running with net tick time as 5 sec. and another
node b@HostIP running with net tick time as 4 times greater than the
other node, on both the nodes a Erlang program is running which will
just print the kernel messages received as node_down or node_up. In the
above scenario the node which is running with more tick time is
receiving node_down_reason as "connection_closed" and the other node
which is running with less tick time is receiving node_down_reason as