Why not change the default behavior to that of port 0, letting the OS select an open ephemeral port if the user doesn’t specify a specific port?
> On Oct 5, 2018, at 9:02 AM, Dan Smith <dsm...@pivotal.io> wrote: > > +1 > > I think it's better not to have the possibility of a port collision for > people using Geode's default settings. Especially if you are using > automation to start and restart geode members, having a member fail to come > up randomly is problematic. > > -Dan > >> On Thu, Oct 4, 2018 at 4:06 PM Brian Rowe <br...@pivotal.io> wrote: >> >> Currently the default value for this parameter covers the default locator >> and server port values. As a result of this, when launching a locator and >> then a server on the same system using gfsh, it's possible to see the >> server fail because the locator has already bound the default server >> socket. We've actually seen a couple of test runs fail with this issue. >> >> The proposed new range is 41000-61000, which, in addition to not >> overlapping the other default port values, has the benefit of being a >> subset of the linux ephemeral ports (for users who care about such >> things). Please let me know if there are any objections to this change. >> >> Here's the current javadoc for this parameter: >> >> Description: The allowed range of ports for use in forming an unique >> membership identifier (UDP), for failure detection purposes (TCP) and to >> listen on for peer connections (TCP). This range is given as two numbers >> separated by a minus sign. Minimum 3 values in range are required to >> successfully startup. >> Default: 1024-65535 >>
