[erlang-questions] New Feature added to Erlang
Mon Apr 1 16:17:29 CEST 2013
It's a clear violation of the isolation principle!
Nodes will be happy until they learn about network latency and then they
will stop using memory from TMALR(The Memory Allocator of Last Resort).
Already affected nodes will free it back to TMALR and a lot of memory will
be unused. To make the IT buyer happy, data structures will be made bigger
in next release. Everyone will think it's working until they notice
memory bandwidth is saturated (processes start using wheelbarrow to just
get a diod flashing). All this mess could be avoided if we start using
On Mon, Apr 1, 2013 at 1:27 PM, Dmitry Kolesnikov <dmkolesnikov@REDACTED>wrote:
> Here is an instruction:
> - Dmitry
> On Apr 1, 2013, at 2:21 PM, Jan Wrobel <wrr@REDACTED> wrote:
> > Help!
> > I've patched this and run on a small Amazon ec2 cluster. Everything
> > worked fine until it started spreading. It somehow got access to the
> > Amazon management console and is allocating new machines. It is
> > already at 1000 Extra Large instances with monthly cost of 370k$! I
> > need to stop this, but it changed the management console password!
> > Wait it is now on my laptop! And my phone! How can I kill this, please
> > he...
> > On Mon, Apr 1, 2013 at 9:48 AM, Joe Armstrong <erlang@REDACTED> wrote:
> >> http://joearms.github.com/2013/04/01/too-big-to-fail.html
> >> /Joe
> >> _______________________________________________
> >> erlang-questions mailing list
> >> erlang-questions@REDACTED
> >> http://erlang.org/mailman/listinfo/erlang-questions
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://erlang.org/mailman/listinfo/erlang-questions
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions