Why the Membership Port in the Artifactory HA Configuration Is Set to "0"

Why the Membership Port in the Artifactory HA Configuration Is Set to "0"

AuthorFullName__c
Batel Tova
articleNumber
000004257
ft:sourceType
Salesforce
FirstPublishedDate
2018-09-06T14:52:11Z
lastModifiedDate
2024-03-10T07:44:58Z
VersionNumber
7

Relevant Versions: This information pertains to Artifactory versions 6.2 and above.

Artifactory features an internal locking mechanism for Artifactory HA configurations. Prior to version 6.2, Artifactory HA used the third-party, Hazelcast library for distributed locking during concurrent operations. Now, Artifactory uses a locking mechanism that relies on the database to provide robustness performance and stability. Therefore, as we are no longer using the membership port, it’s set to zero on the high availability page.