|
|
|
|
|
A list of servers in the cluster.
Add server
Clicking "Add server" will add a new server to the cluster.
On/Off
Indicates whether the server is enabled or not. Clicking the light will toggle on/off. If you disable a server, all users that are currently connected to it (see Connection Timeout) will be redirected to another server the next time they connect.
Online
OctaGate Switch™ will periodically connect to all servers in a cluster to determine if the server is online. If a server can't be reached, it will be flagged as offline and OctaGate Switch™ will no longer send requests to it. The online flag on the server is green if the server is online and enabled, it's read when the server is offline. If the cluster is disabled, the Online LED is grayed.
Server Name
The name of the server. This name is purely for your convenience, and it's not used by the server. But a good name will make your cluster easier to maintain, helping you determine which server is faulty.
Server Address
The address of the server (can be either IP or hostname). This MUST be set.
Server Port
The port that requests should be forwared to on the server. This MUST be set.
If you're evaluating OctaGate Switch™ Load Balancing, but don't have several webservers yet, you can create several servers with the same Server Address but different Server Ports. You will have to start a web server or web application on each port, but that will let you easily try Load Balancing.
Capacity
The capacity indicates how many requests / connections a server can handle, in relation to the other servers in the cluster. The size of the value is arbitrary - you can set it to anything you like, but it must be consitent within the cluster. If server A is twice as fast as server B, then server A should have a capacity rating that's twice as large as that of B.
The Capacity value only effects the number of new sessions a server is assigned, existing sessions are not effected by this value. Setting Capacity to 0 will not kill existing connections to this server, but it will prevent any new sessions from being established. This can be used to perform a soft rollout, where you deploy a new service without killing the old one