ityonemo
I have a GenServer that is tied to a tcp connection; if the connection fails it fails init/1. This is a problem because if the other end of the tcp connection (which is a config-assigned ip address) is down it will prevent the entire application from starting (by crashing up the supervision tree) and I suspect that it will crash the supervision tree as well if the connection is dropped for an extended time (say I’m doing maintenance on that node).
Is there a way to handle slow, scheduled retries at the supervisor level, or should I move the connection attempts outside of init/1, or is there some other best practice that others would recommend to handle connection retries?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
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!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lucaong
If the possibility that the connection fails is something that your system has to handle during normal operations, I’d move the connection logic outside of
init/1, and make theGenServerlogic explicitly deal with the “unconnected” state (for example by trying periodically to re-establish the connection, and responding with errors to calls happening while the connection is down).bottlenecked
Like @lucaong said, it’s better to handle connecting outside your init/1 function. You could try doing that with :continue/handle_continue that will not block the supervision tree from starting up (a good strategy when initialization of a server is expected to be slow) or you could use the Connection GitHub - elixir-ecto/connection: Connection behaviour for connection processes · GitHub lib that makes connection and reconnection handling logic really explicit
Last Post!
ityonemo
sorry, I misspoke, I didn’t mean slow, I meant infrequent. Putting it in
init/1isn’t a problem in the ‘blocking-the-caller’ sense.PS. that library is fantastic, thanks! I might incorporate it.