Skip to content

Conversation

@DomGarguilo
Copy link
Member

Fixes #5845

  • All services now read a new rpc.bind.port Property for their port candidate list. This new prop has a default value of 19000-19999. Individual port props have been removed (*_CLIENTPORT properties)
  • When only one port is set for this property, the internal value will have the next 1000 ports appended to allow for the next 1000 ports to be searched for the next open port after the given port
  • The port range syntax is just an inclusive range like M-N

All the changed tests and ITs pass and so does the sunny maven profile.

@DomGarguilo DomGarguilo added this to the 4.0.0 milestone Oct 30, 2025
@DomGarguilo DomGarguilo self-assigned this Oct 30, 2025
@DomGarguilo DomGarguilo requested a review from ctubbsii October 30, 2025 19:49
@dlmarion
Copy link
Contributor

Is there an example for how a user would configure ports for the individual servers? There is a comment in #5845 about setting this in accumulo-env.sh, but I'm not sure that will work. I'm thinking about the case where there are multiple tservers or compactors running on the same host. With the current configuration you can make sure that tservers are allocating ports from set A and compactors from set B. I think with this new configuration, all processes on the host will be allocating ports from a single set of available ports.

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

Successfully merging this pull request may close these issues.

Simplify bind port configuration for servers by supporting a port range property type

2 participants