Open erlang port range up to support greater than 2 nodes in a cluster

[chriswiggins]

Overview

Erlang portrange in 2.1.1 vm.args was restricted to a single port. This changes that so more than 2 nodes can be supported in a cluster

Testing recommendations

Run the docker container with the new vm.args

GitHub issue number

N/A

Related Pull Requests

N/A

Checklist

• Code is written and works correctly;
• Changes are covered by tests;
• Documentation reflects the changes;

[wohali]

This is actually not necessary. See c726be0

As long as you're only running one node per container, you only need one port open.

[chriswiggins]

I disagree. This won’t work if you’re doing —net=host On 28/11/2017, at 5:32 AM, Joan Touzet <notifications@github.com<mailto:notifications@github.com>> wrote: Closed #46<#46>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#46 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACsxEVdd30kgAzFQeFymMH9OYv6HxNzxks5s6uQbgaJpZM4QrGlt>.

[wohali]

Oof. You're right, but that's not a recommended deployment scenario. You always want the Erlang distribution traffic to be on a private network, as much as possible. Why wouldn't you leverage the mechanism Docker already has in place for that?

[chriswiggins]

@wohali I'm running the docker container on 3 separate VMs, which are on the same Layer-2 network segment, but different hosts. They can't share private docker networks (to my knowledge anyway but happy to be proven wrong!) Unless I'm deploying this in a weird fashion? My docker hosts are statically configured so there is no orchestration going on under the hood, just my fingers on the keyboard and the CLI!