[erlang-questions] simple_one_for_one supervisor - what happens at restart? (also: gen_tcp)
Sun May 15 02:41:56 CEST 2016
I'm glossing over these responses, but the points about gproc raises
an issue I had with some earlier responses - that plugging a process
into a supervisory hierarchy lets you somehow keep track of it. I
don't think that's good advice - querying supervisors is a bad idea.
If you want to track processes, use gproc.
gproc should be in core IMO - at least the publish/discovery facility
for processes. Though maybe I've missed a recent update.
On Sat, May 14, 2016 at 12:24 PM, Ryan Stewart <> wrote:
> Oliver, gproc looks exactly right; thanks for the pointer! I just didn't
> know about it, so essentially I was building my own with very limited
> features. Pardon my ignorance. I've been working in Erlang for a little over
> 2 years, and I only just feel like I have a handle on how everything fits
> together. I still don't know what all libraries are out there to do common
> Hmm, that seems like a good subject for a fresh thread...
> On Sat, May 14, 2016 at 12:16 PM Oliver Korpilla <>
>> Hello, Ryan.
>> Isn't this normally the job of a registry like gproc or am I
>> misunderstanding your requirements?
>> I usually start the worker dynamically through the supervisor and let it
>> do its own registration.
>> Gesendet: Samstag, 14. Mai 2016 um 18:57 Uhr
>> Von: "Ryan Stewart" <>
>> An: "Loïc Hoguin" <>, Chandru
>> Cc: "Erlang-Questions Questions" <>
>> Betreff: Re: [erlang-questions] simple_one_for_one supervisor - what
>> happens at restart? (also: gen_tcp)
>> On Sat, May 14, 2016 at 3:28 AM Loïc Hoguin <> wrote:The
>> primary function of supervisors is to provide a hierarchy of
>> processes belonging to an application. With such a hierarchy it becomes
>> possible to find and query information about any single process in your
>> system in a standard manner.
>> I'm rather interested in this aspect of supervised processes. Especially
>> in the case of a simple_one_for_one supervisor, it's unlikely that the
>> supervised processes will be registered, and it's possible that there could
>> be a rather large number of them--maybe in the tens or hundreds of
>> thousands, depending on the use case. I'm curious how others deal with
>> finding a specific temporary process if, for instance, you want to check on
>> the progress of the work it's doing.
>> My current solution is to have a locally registered "manager" process as a
>> supervised sibling to the SOFO worker supervisor, and the manager just has a
>> dict that maps UUIDs to worker PIDs. I.e. creating a "worker" process
>> entails both a supervisor:start_child() call and storing the worker id ->
>> pid mapping in the manager. Is this a typical way to handle temporary
>> workers?_______________________________________________ erlang-questions
>> mailing list
> erlang-questions mailing list
More information about the erlang-questions