marcin

marcin

I’m implementing a controller that schedules a background job and returns.
The job itself is implemented as a GenServer Foo.

I wanted this to be reliable, so that if Foo fails, it is restarted, different Foo jobs are distributed, and that I have a track record of what went wrong and right.
Coming from ruby I wanted similar guarantees to Sidekiq, and so I decided I’ll use Oban workers.

I created an Oban worker that start_links to the GenServer Foo and waits using receive for a message from Foo, that it has completed its job.

I thought that if Foo dies, the worker will die as well and Oban will restart it. Wrong: Oban worker will only be restarted if it raises and error, not if it gets killed.

So instead, i did Process.monitor on Foo’s pid, and I’m checking if the message from Foo is the completion message, or : DOWN message. If it’s the latter, I’m raising an exception so Oban retries this job later.

This works but I feel like suddenly I’m implementing some kind of supervisor mechanism and I should probably use mechanisms that are already present in Elixir. What would you suggest here? Also the necessity to pass “call me back” pid to Foo so it sends back information about successful completion seems like unnecessary coupling. Maybe this is not the case for using Oban?

For those interested in details: the job is to download a huge file and process it. The controller endpoint just accepts the URL of huge file and schedules this job.

Showing Posts 1 to 1

sorentwo

sorentwo

Oban Core Team

Is this the only place you’re using the Foo gen server? If so, perhaps you don’t need to use a separate GenServer or process at all. Each job in Oban runs as an isolated process already.

This can work, you’d just need to call Process.flag(:trap_exit, true) within the Oban job to ensure that it receives an :EXIT, pid, reason message rather than crashing the process. By default Oban jobs do not trap exits.


Sending messages between processes will always add a little bit of complexity: passing pids, sending messages and monitoring are par for the course. If possible, I’d first try to put all of this within a single process. Failing that, I would try to use a Task rather than a GenServer and simplify the message passing.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews