Load Balance (Control Center)
If the additional module Load Balancing is used, all nodes that are currently registered at the node controller are displayed here (the node controller is the _data at which you are currently logged in here, since normal nodes do not have GUI access). If the selected delegation model is not 'round robin', the current load factor will be shown instead of 0.0.
(1) You can perform a connection test between the node controller and this node.
(2) 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.
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).
Both can also be triggered via HTTP.
(3) You can disable or enable a node, i.e. an enabled Lobster_data node will take part in the load balancing and a disabled one will not. Alternatively, you can take a node out of the job distribution, i.e. it will not receive any jobs.
Note: If a node fails, the jobs assigned to it can be taken over via another context menu entry.
Note: See also section Patching During Load Balancing Operation .
(4) Here you can edit the file lb_node.properties. See section Failover Concept.
(5) See parameters requestSize and statisticThreshold in section Configuration of a Lobster_data Node.