Skip to content
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

Storage Units Port range customization #176

Open
aravindavk opened this issue Apr 10, 2022 · 3 comments
Open

Storage Units Port range customization #176

aravindavk opened this issue Apr 10, 2022 · 3 comments

Comments

@aravindavk
Copy link
Member

Global option to customize the Port allocation range.

kadalu config PROD storage-unit-port-start 5001
kadalu config PROD storage-unit-port-end 5100

Take start + 100 if the storage-unit-port-end is not configured.

@leelavg
Copy link

leelavg commented Apr 10, 2022

  • Out of context, I don't know what above does however why not range with a single config op?
    kadalu config PROD storage-unit-port-range <start>-<end>

@aravindavk
Copy link
Member Author

  • Out of context, I don't know what above does however why not range with a single config op?
    kadalu config PROD storage-unit-port-range <start>-<end>

Looks good. Thanks.

When a Volume is started, each Storage Unit process(Brick Process) will get a Port. GlusterFS allocates the Brick ports dynamically on every restart of a Brick process. Kadalu/Moana decided to allocate Port once at the time of Volume creation and never change on Storage unit restart.

The Hardcoded port range used by Moana is 49252-49452 (https://github.com/kadalu/moana/blob/main/mgr/src/server/datastore/ports.cr#L16). With the above-proposed option, the user can configure the range.

GlusterFS uses 49152-60999 (https://github.com/gluster/glusterfs/blob/devel/extras/firewalld/glusterfs.xml#L13)

@aravindavk
Copy link
Member Author

CLI should warn with something like the below,

$ kadalu config <POOL> storage-unit-port-range <start>-<end>
Port range updated successfully. Please note that this
configuration will not change the Ports that are already
allocated for existing Volumes.

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

No branches or pull requests

2 participants