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

Start going multi node #37

Merged
merged 8 commits into from Apr 22, 2018

Conversation

1 participant
@oestrich
Owner

oestrich commented Apr 18, 2018

  • Each node starts a Game.World.Master process and tries to elect
    itself as a leader
  • The winning process will start zones on the other nodes
  • Uses libcluster to get nodes connected on boot
  • Uses swarm as a global registry for :via tuples

libcluster configuration:

config :libcluster,
  topologies: [
    local: [
      strategy: Cluster.Strategy.Epmd,
      config: [hosts: [:"world1@localhost", :"world2@localhost"]]
    ]
  ]

oestrich added some commits Apr 17, 2018

The start of spanning multiple nodes
- Each node starts a `Game.World.Master` process and tries to elect
  itself as a leader
- The winning process will start zones on the other nodes
- Uses libcluster to get nodes connected on boot
- Uses swarm as a global registry for `:via` tuples

@oestrich oestrich self-assigned this Apr 18, 2018

oestrich added some commits Apr 18, 2018

Small tweaks to get tests passing
Also try to disable the 5 second wait that seems to be happening at the
start of the test suite. Dev mode has it, I think its swarm warming up
waiting for nodes to be booted.
Switch to `:global` for name registration
Swarm was over greedy in restarting, remove elixir registries

@oestrich oestrich merged commit 51f500e into master Apr 22, 2018

@oestrich oestrich removed the in progress label Apr 22, 2018

@oestrich oestrich deleted the multi-node branch Apr 25, 2018

@oestrich

This comment has been minimized.

Owner

oestrich commented Apr 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment