1stSolo
I have a usecase where kafka endpoind information is entered by user. The endpoint is bound into Brod Client I’m starting and if that succeeds I start a Producer from that Client. If something fails, the GenServer is configured to do restart: :permanent. Which is a good thing because you want your client to try to restart if connection is severed or GenServer crashes for any reason. BUT since user entries are not fool-proof, a bad input such as non-existent Kafka broker will put GenServer into permanent restart loop.
How to best handle the situation where I want to avoid creating a client when user enters invalid Kafka configuration, but keep permanent restart mode if the configuration is valid?
Brod is doing it! brod/src/brod_sup.erl at 3.7.9 · kafka4beam/brod · GitHub
Maybe the best protection is to have separate code that validates the endpoint user entry and makes sure it’s live before attempting to start a client instance?..
Where Next?
Trending in Questions
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
- #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
- #graphql
- #ai
- #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.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 2 of 2 Posts
hst337
You can change permanent to transient. This will restart client only if it terminates with abnormal reason. Using this, you can exit with normal reason when the topic name is wrong
1stSolo
Unable.
permanentis hardcoded in Brod library. Only thing you can change is delay between restarts.My solution was to again use Brod to ping the brokers via
get_metadata()and create client and producer only if response was{:ok, _metadata}. Otherwise I don’t create brokers and return:error.