[erlang-questions] Erlang message passing delay after abnormal network disconnection

[Eranga Udesh]

The problem I am talking about occurs while the network is in partitioned
condition. When the network connection is re-established and the Erlang node
is connected with a net_adm:ping/1 the message queue drains out quickly and
the nodes start working normal.

As I said before, this delay occurs only after an abnormal network
disconnection. If the receiving Erlang node is shutdown gracefully, the
message delay doesn't occur.

I doubt, this occurs only when the packets sent out are going to a
black-hole and nobody responds that the destination TCP entity is
unavailable.

- Eranga



On Wed, Mar 5, 2008 at 12:21 AM, Scott Lystig Fritchie <
fritchie@REDACTED> wrote:

> Hi, everyone.  I've read forward in the thread ... and am wondering if
> there's a simpler cause?  Since the default distribution mechanism rides
> on top of TCP, the delay might be caused by TCP's exponential back-off
> when packet loss is encountered?  A quick packet capture could verify
> this theory: there would be a big delay after the network partition is
> fixed (i.e. plug cable back in, "ifconfig {IFACE} up", whatever) and
> before the next packet (in either direction) is transmitted.
>
> -Scott
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080305/0e5fde6e/attachment.htm>