Managing members of a cluster - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services
Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Use the Repo Admin Console for repository server clustering.

Servers connected to the same database instance are usually clustered automatically. In most cases no additional configuration is necessary.

Note: Ensure that clustering is enabled for your license.
  1. Open the Repo Admin Console.
  2. In the Repository Services section, click Repository Server Clustering.

    You see the Repository Server Clustering page.

  3. Set the clustering properties:

    For Host Server:

    Property Description
    Server Name This specifies the name of the host server that you’re currently connected to, for example ip-x-x-x-x.
    Cluster This shows if clustering is enabled or disabled. You need to have a correct license to enable clustering.
    IP Address This specifies the IP address of the server, for example x.x.x.x.
    Cluster ID This specifies the unique id of the server, for example xxxxxx.

    For Cluster Members: Server Details

    Property Description
    Server This specifies the server name of the cluster member, for example ip-x-x-x-x.
    IP This specifies the IP address of the server, for example x.x.x.x.
    Port This specifies the port number of the server, for example 5701.
    Last Registered This specifies the date and time when the cluster member was last started, for example 02-Oct-2013 12:48:37.
    Node Type This specifies the server type, for example Repository server / Hazelcast server.
    Repository IP If the Node Type is Hazelcast server, this specifies the IP address of the linked Repository instance. Otherwise, it will be blank as the Repository IP is already specified by the IP property.
    Number of Members This specifies the total number of members in the cluster, for example 1.

    For Offline Cluster Members: Server Details

    Property Description
    Server This specifies the server name of a previously clustered server member that is no longer a member of the cluster, for example ip-x-x-x-x.
    IP This specifies the IP address of the offline server, for example x.x.x.x.
    Port This specifies the port number of the offline server, for example 5701.
    Last Registered This specifies the date and time when the offline cluster server was last started, for example 02-Oct-2013 12:48:37.
    Node Type This specifies the server type, for example Repository server / Hazelcast server.
    Repository IP If the Node Type is Hazelcast server, this specifies the IP address of the linked Repository instance. Otherwise, it will be blank as the Repository IP is already specified by the IP property.
  4. Click Remove from list to decommission a particular cluster member.

    The offline cluster member no longer appears in the Offline Cluster Members list.

  5. Set the clustering properties for Connected Non-Clustered Server(s):

    In exceptional cases, a server may be connected to the same database as other cluster members, and yet it may not be a member of the repository cluster. In other words, it’ll have clustering disabled. Such a server is called connected non-clustered server.

    Property Description
    Server This specifies the name of the server, for example ip-x-x-x-x.
    IP This specifies the IP address of the server, for example x.x.x.x.
  6. To check if clustering is working properly, click Validate Cluster.

    You see the Cluster Validation page. This page shows the validation results for a cluster.

    Cluster validation performs a check to ensure that communication between the cluster members is working correctly. For a cluster to be considered validated, all cluster members should show success status. If one server fails in a two-server cluster, then both the servers will be marked as failed.

  7. Click Close.