michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the system that is not yet started. I think I cannot re-order the entries in my supervision tree to avoid the problem, because that dependency also relies on Oban to be functional. So it’s a chicken-and-egg problem.
What is the best way to start Oban and have it running without executing any jobs, and only start job processing after some condition passes? An LLM suggested configuring queues to be in the paused state by default, and adding a one-shot supervised child that calls Oban.resume_all_queues(local_only: true) later in the supervision tree
Where Next?
Trending in Questions
Other Trending Topics
Latest Oban Threads
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #ai
- #graphql
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #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.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mudasobwa
I would have started the dynamic supervisor in the main tree and add Oban as its only child after the condition passes.
LostKobrakai
What is that dependency on Oban? To write new jobs? Afaik writing jobs just needs the repo to be up, but none of the Oban processes being started.
sorentwo
The LLM is correct, and likely referencing previous advice we’ve given on this exact topic. This is the exact situation that drove being able to start jobs in a paused state.
Ideally you would have Oban be one of the last dependencies to start to avoid this problem, but that’s not always possible.
That’s not correct, you need Oban started to insert jobs. It doesn’t need to run any queues or plugins, but an instance must be registered.
It is possible to build a raw job changeset and insert it through a repo call, but you’ll loose a lot of functionality and configuration.