Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disappearing values from Horde.Registry after spawning more than two nodes. #258

Open
LKlemens opened this issue Jan 24, 2023 · 2 comments

Comments

@LKlemens
Copy link

LKlemens commented Jan 24, 2023

Problem: disappearing values from Horde.Registry after spawning more than two nodes.

Expected behavior: After adding more nodes, values in the Horde.Registry from all nodes will be synced without losing any value.

Elixir: 1.13.3
horde: 0.8.7

Reproduce:

  • clone and setup project
   git clone https://github.com/LKlemens/horde_behavior
   cd horde_behavior
   mix deps.get
  • start first node
  iex --sname node1@localhost --cookie foo -S mix
  • start second node
  iex --sname node2@localhost --cookie foo -S mix
  • check state of registry on node1 - should be two processes - one per node
  nodes = [node() | Node.list()]
  Enum.map(nodes, fn node -> Horde.Registry.lookup(Registry.State, node); end)
  [[{#PID<0.276.0>, nil}], [{#PID<19886.268.0>, nil}]]
  • start third node
  iex --sname node3@localhost --cookie foo -S mix
  • check state of registry on node1 - should be three processes but there are only two processes - first and last - the middle one disappearing
  nodes = [node() | Node.list()]
  Enum.map(nodes, fn node -> Horde.Registry.lookup(Registry.State, node); end)
  [[{#PID<0.276.0>, nil}], [], [{#PID<21155.273.0>, nil}]]

Notes

Agent.start_link(fn -> 553 end, name: {:via, Horde.Registry, {Registry.State, node()}})
@LKlemens
Copy link
Author

Hi,
@derekkraan I know you are busy and have much more important stuff to do, but could you (if you have time) just confirm that problem is reproducible on your side?
BTW Thank you for your awesome work! :)

@derekkraan
Copy link
Owner

Hi @LKlemens yes, I believe I have reproduced this error in the past.

It will likely be a while before I find time to work on it again.

Hope this answers your question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants