How do we control/reset the next allocation of port for the gluster bricks?
Issue
After converting our volume to arbiter, we noticed that the port range needed to be expanded. This is expected behavior because each brick for every volume on the host requires its own port, and we added a number of arbiter bricks. However, gluster does not appear to be using some of the intermediate ports. We need to be able to control that as we do not want to open the firewall with a larger port range than necessary.
Environment
- Red Hat Gluster Storage 3.*
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.