[erlang-questions] Curious: disparate net_ticktime's
Wed May 21 19:08:35 CEST 2014
The way the net_tick works is that each node commits to sending at least the frequency of messages derived from net_ticktime (the detection time for four lost ticks, if memory serves). The receiving end will need at least one message within (net_ticktime)/4 milliseconds, or it will time out. After 4 consecutive timeouts, it declares the other node unreachable, without actually verifying that it is there (it will have sent ticks, and they may have arrived, but it doesn’t check that).
This means that if there is no traffic between the nodes, there may be problems if one node sends ticks at a lower frequency than that expected by the other nodes.
On 21 May 2014, at 18:49, David Welton <davidnwelton@REDACTED> wrote:
> What does having different net_ticktimes on different nodes cause problems?
> In my case they are all on localhost and respond within a millisecond,
> so it's not that they aren't responding.
> It's not a problem to set them to the same value, I'm just curious why
> it causes such hiccups.
> David N. Welton
> erlang-questions mailing list
Ulf Wiger, Co-founder & Developer Advocate, Feuerlabs Inc.
More information about the erlang-questions