- 01 Sep 2021
- 2 Minutes to read
Managing your Cluster
- Updated on 01 Sep 2021
- 2 Minutes to read
The Cluster Management Page (found under Admin > Cluster Overview) allows you to monitor your instances server components that are configured for load balancing and automatic failover.
Cluster Management is available from ProGet 5.3.16, Otter v3, and BuildMaster v7.
The cluster configuration section displays your current cluster's settings and your primary and backup service components.
The cluster configuration displays:
- How many servers are in the cluster.
- If load balancing is enabled.
- If automatic failover is enabled.
- You can also configure your service components' heart beat frequency and stale timeout.
- What server has the primary service component.
- What server(s) contain backup service components. Note: Backup service components are only available when automatic failover is enabled.
Servers in Cluster
The servers in the cluster section lists which servers and components are included in the server cluster.
The server table displays:
- The server name.
- The operating system and version.
- The IP address configured on the server.
- The ProGet components installed on the server. (Web & Service)
- The health and verification status of each component.
- The current heartbeat status.
- If the software version is in sync.
- If the encryption key is in sync.
- If the machine key is in sync (Web component only).
You can also manually remove a component from the cluster if it is no longer included in the cluster.
You will also see a warning or an error symbol next to the server and component if the component has entered a stale state. The web component stale timeout is based on a 24 hour window. The service component's stale timeout is based on the configuration setting configured to the right of
Note: You can manually add components to test what this page would look like when a cluster is configured by clicking the
manually add a component link at the bottom of the page.
Why is my machine key showing a decryption failure?
This will occur when the machine key is not synchronized across your web servers. See the Load Balancing & Automatic Failover guide to configure this setting.
Why is my Encryption showing a decription failure?
This will occur when the encryption key is not synchronized across your web servers. The encryption key is stored in your configuration file and needs to be the same on all servers.
Why is my web component showing as stale when it is up and running?
The heartbeat on the web component will only update when web requests hit the web server. If there is a 24+ hour break, like over a weekend or sticky session within a load balancer, where traffic is not routed to the web server, the web component may show a stale state.