cjbottaro
In iex…
iex> Task.Supervisor.async_nolink(
MyTaskSupervisor,
fn -> Process.sleep(60_000) end,
shutdown: 20_000
)
Then in a shell, I do…
kill 27282 # The unix pid for iex
In iex, I see this:
[notice] SIGTERM received - shutting down
And then the iex process ends almost immediately. It does not wait for the shutdown: 20_000. What am I doing wrong?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
There’s a few steps here:
When elixir exits, then that will travel downward the supervision tree.
That happens because supervisors always trap exists (for multiple reasons). So when they get an exit signal they try to stop all their children. They do so by sending an exit signal to their children one-by-one, with an timeout before they brutal_kill them. That timeout is the
shutdownyou’re setting. But the time is all you set by that. Once all children are stopped the supervisor itself stops .The child (could be any process, but in your case a task) still needs to decide how to react to exit signals. By default a task does not trap exists it seems, so it just stops when receiving an exit signal. If you want the task to continue and try to finish its workload before being killed by the supervisor you need to enable the
:trap_exitflag.I’m however with you that it’s strange that there’s a default shutdown timeout, when tasks don’t trap exists by default, so usually tasks would just stop immediately anyways.
Also Liked
LostKobrakai
Yeah. Each process is responsible for it’s own behaviour. The supervisor just makes sure that all children are stopped (graceful at first, forceful afterwards). How the children manage being stopped is their responsibility.
LostKobrakai
Without
Process.flag(:trap_exit, true)the process just stops when it get’s an exit signal. You can find this documented quite well here: Process — Elixir v1.20.2