jdj_dk
I’ve got two nodes connected using libcluster. It has been working fine for some time, but suddenly I noticed the Node.list was empty. After manually connecting the nodes again it seems fine.
But my question is: In a production system how can I ensure this doesn’t happen again? Do I manually need to have a task running which checks the Node.list and attempt to reconnect or at least send an email to me letting me know something iffy is going on. Or is there something built into either libcluster (which should be able to heal) or Erlang to solve this for me?
Thanks in advance!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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.
Producing high quality Elixir screencasts since 2017.
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 Posts (oldest first)
- Show All Posts (newest first)
tty
I haven’t used libcluster, however Erlang has a
monitor_nodefunction. I would look into libcluster before implementing anything usingmonitor_nodeto avoid duplicating unnecessary features.I would also investigate why the nodes apparently lost connectivity with each other.
idi527
What strategy are you using with libcluster? I think all strategies that I’ve used try to reconnect on each gossip round, which for me was usually 5 seconds. I’ve looked through some other strategies, and that seems to not be the case for some of them like
Cluster.Strategy.Epmdsince it probably delegates reconnecting to erlang facilities.jdj_dk
I am using the Epmd strategy which I guess explains why no reconnect happens. I will look into changing to Gossip strategy since I don’t use Kubernetes. The cluster is very small so it should be fine!
Thank you for your help