Thank you for all your suggestions!
I choose to reserve some system ports for our services as it has less work
to do comparing to change Gluster cluster config: need to restart Gluster
node one by one and remount volumes of all clients.
Kind regards,
Canh Ngo.
On Wed, Jun 13, 2018 at 8:13 PM,
Try
gluster volume set VOLNAME client.bind-insecure on
and remount clients. If servers refuse connection, you might also have to
set server.allow-insecure to on.
On Wed, Jun 13, 2018 at 9:41 AM, Milind Changire
wrote:
> On Wed, Jun 13, 2018 at 6:12 PM, Canh Ngo wrote:
>
>> Hi all,
>>
>> We
On Wed, Jun 13, 2018 at 6:12 PM, Canh Ngo wrote:
> Hi all,
>
> We run a storage cluster using GlusterFS v3.10.12 on CentOS7. Clients
> (CentOS) are using glusterfs 3.8.4.
>
> We notice when clients mounts bricks of a volume, sometimes glusterfs uses
> system ports (i.e. in port range 0-1024) to
Hi all,
We run a storage cluster using GlusterFS v3.10.12 on CentOS7. Clients
(CentOS) are using glusterfs 3.8.4.
We notice when clients mounts bricks of a volume, sometimes glusterfs uses
system ports (i.e. in port range 0-1024) to connect to remote glusterfsd
port. e.g:
Server:
tcp0
