You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
$ kadalu config <POOL> storage-unit-port-range <start>-<end>Port range updated successfully. Please note that thisconfiguration will not change the Ports that are alreadyallocated for existing Volumes.
Activity
leelavg commentedon Apr 10, 2022
kadalu config PROD storage-unit-port-range <start>-<end>aravindavk commentedon Apr 10, 2022
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 commentedon Apr 10, 2022
CLI should warn with something like the below,