Hello Everyone
I’m working on a project which needs to use dynamic supervisor to support creating genserver based workers .
The code today can fork/spawn a worker and get attached to the parent dynamic supervisor but when i want to terminate i still see the process as part of the dynamic supervisor process.
Here is the code on the same
Dynamic supervisor code
defmodule Testing.WorkerSupervisor do
@moduledoc """
Worker Supervisor to support dynamic workers
"""
use DynamicSupervisor
require Logger
def start_link(_) do
Logger.debug("Starting the Worker Supervisor")
DynamicSupervisor.start_link(__MODULE__, [], name: __MODULE__)
end
@impl true
def init(_) do
DynamicSupervisor.init(strategy: :one_for_one)
end
def start_task_worker(conn_id) do
spec = {Testing.ConnectionWorker, %{conn_id: conn_id}}
DynamicSupervisor.start_child(__MODULE__, spec)
end
def terminate_task_worker(pid) do
Logger.info("Terminating the Worker")
case DynamicSupervisor.terminate_child(__MODULE__, pid) do
:ok ->
Logger.info("Worker Terminated Successfully")
{:error, _} ->
Logger.info("PID not found")
end
end
end
The Processcheck worker who is part of the main supervisor i have this code
defmodule Testing.ConnectionWorker do
@moduledoc false
use GenServer, restart: :transient
state = %{
conn_info: %{
running: [%{
pid: "pid_id",
conn_name: "new worker"
}]
}
}
Enum.each(diff, fn conn ->
Enum.each(conn_info.running, fn run ->
if conn == run.conn_name do
IO.inspect(run.pid)
Testing.WorkerSupervisor.terminate_task_worker(run.pid)
end
end)
end)
When i see the process association with :observer.start i still see the worker attached to the Dynamic supervisor.
Am i doing the implementation wrong here?
Hello welcome,
Try to change this…
use GenServer, restart: :transient
# to
use GenServer, restart: :temporary
… to test if it restarts or not (it should never restart). If not, it means on terminate_child, the worker does not stop with normal status, and so it is restarted because of transient.
BTW I usually stop GenServer from within, with a specific message, or under some conditions, but not from the supervisor itself, and not with terminate_child().
Hi @kokolegorille thanks for your response and just to my knowledge want to know what is the difference between the Dynamic Supervisor terminating its child vs child terminating it self over a call?
and also checking on your suggestion that terminating the child from the genserver it self so was checking around some example for it and saw this
defmodule Server do
use GenServer
def start do
GenServer.start(__MODULE__, [])
end
def stop(pid) do
GenServer.call(pid, :stop)
end
def handle_call(:stop, _from, status) do
{:stop, :normal, status}
end
def terminate(reason, _status) do
IO.puts "Asked to stop because #{inspect reason}"
:ok
end
end
Is this what you are recommending and any directions on how to fetch the child process pid in the supervisor and send a call to the Genserver to stop?
I always use DynamicSupervisor with Registry to help finding those workers by name.
@kokolegorille i’m using the ets tables and saving the genserver pid and the name associated to it and when i’m trying to kill it i’m sending a call to the genserver stop function to shutdown the process in normal mode.
send(PID, :stop)
in the Genserver
def handle_call(:stop, _from, state) do
{:stop, :normal, state}
end
Please advice if i’m doing it in the right way.
The code is ok for stoping the GenServer, althought You might also use a cast instead of call.
The registry is ets based, no real need to duplicate it’s functionality by hand.
@kokolegorille thanks for the reply … your guidance is really helping me and making me love elixir more .
Here is the something i made a change as per your suggestions
@impl true
def handle_cast(:stop, state) do
{:stop, :normal, state}
end
Infact i’m not directly using the ets table but using this library which is kinda wrapper on top of ETS ({:ets, “~> 0.7.3”}) but i will take your suggestions on using registry.
