Re: Events API new Port requirement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
> Hi,
> 
> As part of Client events support, glustereventsd needs to be configured to
> use a port. Following ports are already used by Gluster components.
> 24007          For glusterd
> 24008          For glusterd RDMA port management
> 38465          Gluster NFS service
> 38466          Gluster NFS service
> 38467          Gluster NFS service
> 38468          Gluster NFS service
> 38469          Gluster NFS service
> 49152-49664    512 ports for bricks
> 
> If I remember correctly, 24009+ ports were used by old GlusterFS(<3.4). In
> the patch eventsd is using 24005. Please suggest which port glustereventsd
> can use?(Can we use 24009 port)
> http://review.gluster.org/15189

I guess you can use 24009, but it would be way better to either:

a. use glusterd-portmapper and get a dynamic port 49152+
b. register a port at IANA, see /etc/services
   (maybe we should try to register the 24007+24008 ports in any case)

HTH,
Niels

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux