[erlang-questions] Cause heartbeat timeout

[Dmitry Klionsky]

I faced a situation like this two times.
It was on a 2 CPUs EC2 instances. Heartbeat timeout was 45 secs.

The first offender was zlib:gzip/1 and ~1GB file, the other was ++ over 
two long lists. Both operations took about 1 min to complete.

My explanation is the heart's erlang part can't send the heartbeat to 
the heart port in time because
either the scheduler it's bound to is busy or port I/O is busy/congested.

Hope this helps.

On 11/08/2017 10:13 AM, Dmitry Kolesnikov wrote:
> Hello,
>
> I am trying to debug an issue of node termination by heartbeat timeout and its recovery. I am looking for advice about the reproduction of heartbeat timeout in controlled environment. What is the best approach to freeze Erlang node?
>
> Best Regards,
> Dmitry
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-- 
BR,
Dmitry