<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 22 maj 2014, at 05:27, Scott Lystig Fritchie <<a href="mailto:fritchie@snookles.com">fritchie@snookles.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Ulf Wiger <<a href="mailto:ulf@feuerlabs.com">ulf@feuerlabs.com</a>> wrote:<br><br>uw> This means that if there is no traffic between the nodes, there may<br>uw> be problems if one node sends ticks at a lower frequency than that<br>uw> expected by the other nodes.<br><br>AFAIK, this can also be tickled by a very large message sent between<br>nodes and the network is "slow enough"(*). The inet_drv driver may be<br>busy transferring data in the middle of that message, but that busy-ness<br>does not affect the ticktime ticker thingie.<br><br></blockquote><div><br></div>That should really be fixed. Why ticking if there is traffic going on between nodes?</div><div>Looking in dist_util.erl there is plenty of code trying to cope with that situation.</div><div>I guess if the send kernel buffers are large and the link is weak that may happend</div><div>anyway. Or ?</div><div><br></div><div>/Tony</div><div><br></div><div><br><blockquote type="cite">-Scott<br><br>(*) It might be that 1Gbit/sec Ethernet or 100Mbit/sec Ethernet is just<br>too slow to transfer a 3 Gbyte Erlang term(**). Or you've been bitten<br>by a congested network that's dropping packets. Or something else.<br><br>(**) This has never, ever, accidentally happened in a Riak cluster, oh,<br>heavens, no.<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: Geneva, Arial, Helvetica, sans-serif; font-size: 12px; ">"Installing applications can lead to corruption over time. </span><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: Geneva, Arial, Helvetica, sans-serif; font-size: 12px; ">Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix"</span></div><div><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: Geneva, Arial, Helvetica, sans-serif; font-size: 12px; "><br></span></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>