Click the System tab.
Select System Status from the System list, and then click System Health.
The overall system health is shown in the top section of the page by the following indicators:
Overloaded—The indicator changes color depending on the overload condition of the system:
Green—No servers are overloaded, and all servers are operating at normal capacity.
Yellow—One or more servers are overloaded, but at least one server is not. Overloaded servers operate at diminished capacity until they are no longer overloaded.
Red—All servers are overloaded and operating at diminished capacity.
Tasks / hour—This displays the current hourly task rate, based on tasks done in the past minute.
Threshold exceptions—This displays the hourly rate of tasks that exceed the threshold time set for each job on each server, based on tasks done in the past minute.
To view the performance data for an individual server, select the address of the server from the list in the Server Health section. The following data are shown for overall server performance:
Task Count—This displays the number of jobs running on the server over time.
Overload / hour—This displays the hourly rate of overload events. An overload event occurs when more tasks are sent to the server than the currently configured design load and ends when the number of tasks is reduced to the currently configured recover load.
| Note: For more information about design load and recover load, see Tuning the load balancer for unequal servers. |
The following task-specific data are shown for the task selected from the list:
Task / hour—This displays the current hourly task rate for the selected task, based on tasks done in the past minute.
Threshold exceptions / hour—This displays the hourly rate of task that exceed the threshold time set for the selected task, based on tasks done in the past minute.
| Note: To change the threshold time for the selected task on the selected server, type a new value beside “Set threshold (seconds),” and then click Apply. |
To zoom in any of the performance graphs in the Server Health section, click the graph. Click the graph again to return to the view of all graphs.
Notes:
A server that meets recommended requirements is tested to process 30 concurrent jobs from clients. If a server is faster than the recommended system, then you may be able to raise the limit on concurrent jobs for that server to increase system capacity. If a server is slower than the recommended system, then you may need to lower the limit on concurrent jobs to maintain system reliability.
| Warning—Potential Damage: Setting high limits on concurrent jobs could cause failures with some solutions, including errors, timeouts, very slow system response, and database failures. Make sure databases are properly backed up before raising limits for concurrently running tasks. |
The adjustment shown here sets the baseline design load for the server. Additionally, a recover load is set at 80% of the design load. When the jobs running on the server exceed the design load, the server is considered to be overloaded, and the load balancer reduces job submissions to the server until the recover load is reached.
Do the following for each server for which you want to change the limit on concurrent jobs:
From the System Health dashboard, select the address of the server from the list in the Server Health section.
Adjust the Concurrently Running Task Limit slider to the desired limit for the server.
| Note: These settings are not saved during an upgrade. If you upgrade your system, then you must repeat these steps. |
When all servers in the system are approximately equal, server loads should be optimal without manually tuning the load balancer. However, when servers are unequal, the least powerful machine determines the overall throughput unless you compensate by manually assigning a load balancing factor to each server. Since more powerful machines can run more concurrent jobs and complete each job in less time, routing more traffic to them increases the overall job capacity of the system.
The load balancer component is composed of three different Tomcat load balancing workers that separately manage Lexmark Management Console (LMC) sessions, job submissions from e-Task 2 and e-Task 3 printers, and job submissions from e-Task printers. The adjustment shown here affects the e-Task 2, e-Task 3, and e-Task load balancers, but not the LMC load balancer. Each load balancer distributes jobs to servers in proportion to the load balancing factors assigned to each server. For example, in a system with three servers with load balancing factors of 10,10, and 20, the first two servers each receive 25% of jobs, and the third receives 50%.
The ideal job distribution depends on the hardware, network environment, and the solution being run. The optimal proportions for load balancing factors can be found by running performance tests on each server. However, some factors such as memory, number of processors, or CPU speed may suggest an initial value for the load balancing factor to add more system capacity. Note, however, that performance improvements are not linear functions of numerical improvements in hardware.
Perform the following steps on each server after initial values are determined for load balancing factors:
From the System Health dashboard, select the address of the server from the list in the Server Health section.
Adjust the Load Factor slider to the desired load balancing factor for the server.
| Note: These settings are not saved during an upgrade. If you upgrade your system, then you must repeat these steps. |
When using more than one server in a system, you can assign some servers to only run LMC and other servers to only process jobs. When all servers are separated in this manner, it is usually adequate to assign only one server to run LMC.
When using a configuration 1-N, X-N, or X-Y-N system with the recommended hardware, it is recommend to do the following:
Install the server component on the RAID 1 array where the operating system is installed on the load balancer computer, and configure it to only run LMC.
Configure servers installed on dedicated computers to only process jobs.
Launch JK Status Manager from your Web browser using the URL , where is the computer where your load balancer is installed.
Server information and the worker status for each of the three load balancing workers appear. Each server in the system is listed as a worker in each Balancer Members list.
For each server that should only process jobs, stop the associated worker on the adminloadbalancer load balancing worker, which balances requests to LMC:
In the “Worker Status for adminloadbalancer” section, click E beside the server name.
For Activation, select the Stopped option.
Click Update Worker.
For each server that should only run LMC, stop the associated worker on the clientloadbalancer and adaptorloadbalancer load balancing workers, that balance job requests:
In the “Worker Status for clientloadbalancer” section, click E beside the server name.
For Activation, select the Stopped option.
Click Update Worker.
Repeat these steps for the same server in the “Worker Status for adaptorbalancer” section.
Notes:
When using three or more servers, reducing the chunk size may increase the speed of device discovery and policy updates.
Click the Services tab.
Select General from the Services list.
Select Parameters from the Tasks list.
In the ChunkSize field, type a new value. When using three or more servers, a value as low as may be appropriate.
Click Apply.