Need help with other JFrog products?
The table columns are as follows:
|Unique descriptive name of the server.|
|The time that the server was started .|
|The context URL that should be used to communicate with this server within the cluster.|
|The port that should be used to communicate with this server within the cluster.|
The current state of the server as follows:
The role of the server as follows:
|The last time this server signaled that it is up and running. By default, each node signals every 5 seconds.|
|The Artifactory version running on this cluster node.|
|The Artifactory revision number running on this cluster node.|
|The Artifactory release running on this cluster node.|
Monitoring for Unresponsive Nodes
You can use the Last Heartbeat field to identify unresponsive nodes. If a node abruptly stops working (e.g. system crash on the server), then it may not be able to correctly update its State value, and will continue to appear as Running.
However, since the server Heartbeat does not get updated for a long interval of time, it is displayed in red with a warning sign as displayed below.
In this case you should check that the corresponding server is up and running and fully connected to your HA cluster and the database.
Removing an Unused Node
If you remove a node from your cluster, it will still appear in your database and will therefore be displayed in the list of cluster nodes.
To avoid confusion you should remove it from your list of cluster nodes (and detach it from the database) so that it doesn't interfere with normal cluster behavior.
To do so, hover over the corresponding server from the list and click "Delete".
When to remove a node
The "Remove" button is only available once a node has not signaled a Heartbeat for a "long" time.
We recommend that you only remove a node from your list if it has indeed been removed from your system.
In case of an error in one of the nodes, or if a node is shut down for maintenance, the Heartbeat will not be updated and Artifactory will alert you to this as described in the previous section.
In this case there is no need to remove the node from your list. Once you fix the error and restart the server the Heartbeat will be updated and the warning will be dismissed.