arjan
I created a tiny library which supervises “singleton” processes, using Erlang’s global module.
Processes which are started with Singleton.start_child/3 are guaranteed to run on one single node in your Elixir cluster. The nodes that don’t run the process, monitor it so that when it dies, it gets respawned, possibly on another node. This monitoring part is something that global doesn’t do for you.
It feels a bit “thin” for a hex package but I find it kind of useful (I’m using it as part of a bigger project, obviously). Anyway, check it out: GitHub - arjan/singleton: Global, supervised singleton processes for Elixir · GitHub
Where Next?
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #elixirconf-us
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
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.
Elixir, Erlang & BEAM conferences from Code Sync. Next: ElixirConf EU 2027
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Tuxified
Sounds useful, thanks. Might be something for a lighting talk? Judging by the amount of hex packages, perhaps even a
Arjans toolbox-talkbodgix
Hi.
Thanks for putting the library together.
Before I found it, I’ve been trying to hack my own implementation and I ended up with a very similar code as yours.
However, both your code and mine suffers from an unexpected behavior.
When a 2nd node joins the cluster, I do see:
But what is unexpected is that not only the singleton process is terminated, but the whole application on one of the nodes:
And one of the nodes basically is left in a state where my own application is not running, only the “libraries” continue running.
I’ve been struggling with the same issue in my own implementation.
I created a DynamicSupervisor for the singleton process, similarly to you and I was hoping that it will “shield” the main Application supervisor from crashing when the :global registry kills one of the singleton processes.
However, that doesn’t seem to be the case and the whole application dies regardless of multiple layers of supervisors
Using Elixir version 1.12.3
Abdallah94
@bodgix have you managed to solve this issue? we’re facing the same problem
al2o3cr
What is
restartset to in the “singleton” GenServer? If it’s set to the default:permanent, then the supervisor on the joined node will keep restarting the process over and over again until it also gives up, cascading down the chain of supervisors until the whole application stops.Does the behavior change if you specify
use GenServer, restart: :temporary?