[erlang-questions] exec-port crashing
Wed Dec 2 18:30:19 CET 2015
Erlexec has been running in several production systems. Yet, I can't claim
that it's bug free as the application has many non-trivial features and
handles various edge cases. So if you find an issue, patches are welcome.
It may become a bottleneck if you heavily rely on redirection of standard
I/O streams of spawned processes, in which case erlexec does the I/O
marshaling between file descriptors. If that's the case, I suggest to
redesign your application, so that it conveys I/O to Erlang by some other
means, freeing erlexec from the role of being the "broker" and leaving it
to do its main function - process supervision.
On Tue, Dec 1, 2015 at 6:36 PM, Alberto Rosso <flagg.abe@REDACTED> wrote:
> Hello guys,
> our erlang application is running several c nodes and shell scripts,
> handled by erlexec. For some reason i'm going to debug deeper, the port
> exec-port crashes when decoding a string received from the erlang side.
> This issue brought a couple of questions to light.
> Isn't it bad to use exec-port as the unique gateway for all of my c nodes?
> I mean, a single crash of the exec-port frustrates the advantages of the
> supervision tree we've designed to make the application robust to hardware
> Another doubt is about the possibility for exec-port to become a
> performance bottleneck of the whole application, as the number of c nodes
> (and their throughput from/to the erlang app) is growing.
> Could be starting more than one instance of the exec application, an
> (awful) solution?
> Your thoughts are really appreciated.
> Alberto Rosso
> save a tree: please don't print this email unless strictly necessary
> L'esperienza e la filosofia che non generano l'indulgenza e la carità sono
> due acquisti che non valgono quello che costano. (Alexandre Dumas figlio)
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions