[erlang-questions] exec-port crashing

Alberto Rosso flagg.abe@REDACTED
Wed Dec 2 00:36:14 CET 2015


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
faults.
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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20151202/8c2e9a81/attachment.htm>


More information about the erlang-questions mailing list