Why the membership port in the HA configuration is set to 0?

From Artifactory version 6.2.0 Artifactory enhances an internal locking mechanism for Artifactory HA setups to provide more stability.

Prior to this version, Artifactory HA used the third-party Hazelcast library for distributed locking during concurrent operations. From this version, Artifactory introduces a new locking mechanism relying on the database to provide added robustness and stability.

Therefore we are not using the membership port anymore and it is set to zero on the high availability page