If the additional module Load Balancing is used, all Working Nodes that are currently registered at the Node Controller are displayed here (only the Node Controller has GUI access). If the selected delegation model is not round robin, the current load factor will be shown instead of "0.0".

Settings

(1) Edit: Here you can edit the file "lb_node.properties". See section Configuration of a Node Controller.

(2) List below: All Nodes. See following section "Context menu".

(3) Threshold / Max jobs in queue: See parameters "controllerThreshold" and "controllerRequestSize" in section Failover concept .

Context menu

Connection test	You can perform a connection test between the Node Controller and this Working Node.
Shutdown system	Self-explanatory.
Become Node Controller	A Working Node can be manually made the new Node Controller. Important note: If the previous Node Controller was a Node Controller by license and configuration, it terminates and can only be restarted manually (i.e. not via the GUI, but on the computer on which the previous node controller is installed). If the previous Node Controller was a Working Node by license and configuration, then it automatically restarts as a Working Node.
Get failover information	You can also get information about the failover status (shows the current Node Controller and all Working Nodes and the order in which they take over its role in the event of a Node Controller failure).
Forced to be Node Controller on next restart	Forces this Node to be the Node Controller when restarting.
Exclude Node from job scheduling	You can take a Working Node out of the job distribution, i.e. it will not receive any jobs. Note: See also section Patching during Load Balancing operation.
Log off and remove Node	Node is completely removed from the Load Balancing. Note: See also section Patching during Load Balancing operation.
Take over jobs from defective node	If a Node fails, the jobs assigned to it can be taken over by another Node.